How we are iterating on Group Single Sign On for GitLab.com
Jan 17, 2019Eric Brinkman
Summary
This post details the initial MVC launch of SAML-based SSO for groups on GitLab.com, acknowledging its limitations and the need for further iteration. It highlights the prioritization of enterprise features like SSO for GitLab.com, the challenges faced by the Manage team due to security issues and broad scope, and the organizational growth plans to address these. The post also mentions the launch of the HackerOne Bug Bounty Program to improve security velocity.
More from the SAML Single Sign-On (SSO) Integration trail
- A leaked personal access token shouldn't expose every project its owner can reach. Fine-grained PATs scope each token’s permissions to the job.
- Passkeys now available for passwordless sign-in and 2FA on GitLab
- How to set up GitLab SAML SSO with Google Workspace
- Strengthening GitLab.com security: Mandatory MFA
- Automating role-based access control (RBAC) at scale