Setting Up SAML2 Federated Single Sign-On (SSO)
As IdPs come in all shapes and sizes, the following topic discusses in general what you must do to configure Federated SSO. As you will see in the description below, the person in your organization responsible for managing your IdP will need to interact with Codefresh support team to successfully set up a trust between your IdP and Codefresh SP.
Before you set up Federated SSO:
- Have your account set up with Codefresh enterprise plan
- Ensure you have a working SAML 2.0 compliant Identity Provider (IdP).
- Identify someone in your organization who is familiar with configuring and managing your organization’s IdP.
- Ensure that your IdP’s system clock is synchronized with a reliable time source. If it is not, tokens generated will be unusable and SSO will fail.
Summary of Federated SSO Setup
Codefresh expects the following user attributes to be passed through SAML between your Idp and Codefresh SP:
- User email address
- User first name
- User last name
- User full name
- User unique id that isn’t subject to change in your identity managment environment
How does the connection process works?
Once Federated SSO has been configured, the process works as follows:
Steps 2 to 7 happen in the background, and are transparent to the user.
- A user logs in to Codefresh and enters their email
- The user is redirected to Codefresh Service Provider (SP) to initiate SSO.
- The user’s browser is then redirected to the customer IdP.
- Once authenticated by the corporate side, a SAML token is sent to the user’s browser.
- The SAML assertion is then forwarded to Codefresh SP.
- If you are a valid Codefresh user for this SSO connection, an SSO token is returned to the user’s browser.
- The user’s browser then returns a token to Codefresh and access is granted for your account.