This document explains the process to enable SSO for DeepSource using SAML 2.0 with Okta as the Identity Provider (IdP).

SAML-based Sign-on

Configuring SSO on Okta

For now, an admin (on Okta) needs to create a custom SAML integration for DeepSource Enterprise. The steps for which are as given:

1. On the left sidebar, choose "Applications" → "Applications", and click on "Create App Integration".

2. Choose "SAML 2.0" and click "Next".

   

3. Fill in the following details:

   

   Field	Value
   App Name	DeepSource Enterprise Server
   App Logo	Upload this logo and click "Next"

4. Assuming that DeepSource is hosted on "https://deepsource.foobar.com", fill in the following details accordingly:

   

   Field	Values
   Single sign on URL	https://deepsource.foobar.com/saml2/acs/
   Audience URI (SP Entity ID)	https://deepsource.foobar/saml2/metadata/
   Name ID format	EmailAddress (choose from drop down)
   Application username	Email (choose from drop down)

5. In "Attribute Statements", add the following:

   

   Field	Name format	Value
   first_name	Basic	user.firstName
   last_name	Basic	user.lastName

6. Under Feedback selection, choose:

   1. For "Are you a customer or partner?", choose "I am an Okta customer, adding an internal app".
   2. App type: check the box — This is an internal app that we have created. Otherwise, Okta will ask for many other fields. Click on "Finish".

7. On the next screen, go to the “SAML Signing Certificates” section. Copy the link for "Identity Provider Metadata" by clicking on Actions -> View IdP metadata for the “SHA-2 Type” certificate.

   

   <aside> 💡 It should be in the following format: https://<customer>.okta.com/app/<app-slug>/sso/saml/metadata

   </aside>

Changes on Kotsadm

Once SAML has been configured on Azure AD, navigate to “Config” tab in the Admin panel (replicated Kotsadm):

1. Check "Yes" for "Enable SAML SSO".
2. Enter the URL copied in Step 7 above for "IdP metadata URL".
3. One last piece of configuration is whether you want to enable social authentication (i.e. allowing users to be created/log in with GitHub) alongside SAML. In this case, users will be allowed to either sign in via SSO or via OAuth. Choose accordingly.