Troubleshooting user authentication (SSO)
As of 3.20, Sourcegraph supports 6 authentication methods as listed in our User authentication (SSO) page, details about how to configure those methods should refer to the relevant document pages.
Among these authentication methods, there are 4 that require Sourcegraph to send requests to the authentication provider, including GitHub OAuth, GitLab OAuth, OpenID Connect and SAML.
If a GitHub OAuth method is configured in Sourcegraph, users should be redirected to the GitHub instance (GitHub.com, GitHub Enterprise, etc.) to authorize the Sourcegraph OAuth application upon sign in. Once the user is authenticated on the GitHub instance and has authorized the application, the GitHub instance should redirect the user directly back to the Sourcegraph instance.
This redirection contains critical and confidential information that Sourcegraph consumes (as an OAuth consumer), and information may be stripped or expired if there is a third-party in the way.
Therefore, the Callback URL/Single Sign On URL is very important to get right on the authentication provider side. Here is an example of callback URL in a GitHub OAuth application settings:
For an OAuth application against GitHub.com (GitHub OAuth), the authentication flow should look like this (-> indicates a browser redirection):
Sourcegraph (choose to sign in with GitHub.com) -> GitHub.com (authorize the application) -> Sourcegraph
The authentication provider always redirects back to its direct consumer
GitHub OAuth, GitLab OAuth, OpenID Connect and SAML all require the admin to configure a Callback URL/Single Sign On URL on the authentication provider side, which means the redirection back to the Sourcegraph (the consumer) is critical to make the user authentication work (as explained in the last section).
In a complex authentication set up, there is a chain of authentication. For example, Sourcegraph syncs users from the GitHub instance via GitHub OAuth, and the GitHub instance in turn syncs users from a company central SSO (such as Okta) via SAML.
In such a setup, the Sourcegraph instance only talks to the GitHub instance, and is not aware of the existence of the central SSO. The central SSO, in turn, does not know that the Sourcegraph is syncing users from the central SSO (through GitHub).
Therefore, it makes no sense to have the central SSO redirect users directly back to Sourcegraph, which effectively bypasses the GitHub instance. The authentication provider should always redirect the user to its direct consumer. Thus, the central SSO should only redirect users back to the GitHub instance, and the GitHub instance should redirect the user back to Sourcegraph with any information needed for the consumer.
Make sure the client ID and client secret are actually correct
Invalid client ID and client secret pair does not prevent the user from completing the OAuth flow until a confusing error, which may mislead the user into thinking the client ID and client secret pair are correct.
Test in incognito mode
It is possible that a user’s browser extension modifies or strips a HTTP header or cookie needed for the authentication. Ask the user to perform the test in incognito mode without any browser extensions. The incognito mode also helps ensure that the user is logged out from all involved parties.
Preserve log in DevTools
To keep a record of redirection in a user’s browser is very helpful to audit the auth flow. Here is how to do it in Chrome:
It’s easier to spot problems if the user “clears logs” before running tests:
Configure SAML in Okta
Things to note:
Okta has a weird UX that many options (e.g. SAML templates) are not available in the so-called Developer Console UI. Make sure to first change to the Classic UI on the top left.
The Okta docs must be opened directly from the application settings because of a special URL parameter
baseAdminUrlused to display confidential information in the docs:
Without the URL parameter
baseAdminUrl, it displays a static warning:
Sourcegraph specific cookies
For GitHub OAuth, Sourcegraph uses a special cookie called
github-state-cookie, which should be sent by browser automatically when the user redirected back to Sourcegraph (the callback URL):
If the cookie is not found in the Request Headers, then there is a problem. It may be due to proxy server stripping out any unrecognized cookies (so the browser won’t be able to receive the cookie back from the Sourcegraph instance in the first place).
Things to collect for async analysis
"auth.providers"portion of the Sourcegraph site configuration. Example:
A screenshot of the Sourcegraph OAuth application on the GitHub instance. Example:
A screenshot of the GitHub authentication settings.
For GitHub Enterprise Server, it is in the management console’s Settings > Authentication. Example:
For GitHub Enterprise Cloud, it is in the organization’s Settings > Organization security > SAML single sign-on. Example:
Screenshots of the Okta application settings on both General and Sign On tabs, with all options from top to bottom.
Full browser logs (https://toolbox.googleapps.com/apps/har_analyzer/)