Okta SSO

Set up Okta single sign-on (SSO) on Sentry.

  1. Sign in to your Okta organization with your administrator account.

  2. From the admin console's sidebar, click Applications > Applications, then click on "Browse App Catalog" (or "Add Application" for the old interface).

  3. Search for Sentry, then click "Add" to be brought to the setup wizard.

    Sentry in Okta Gallery of Integrations

  4. Provide the settings. Note that for "1. General Settings", you will not need to provide any special settings. For "2. Sign On Options", provide the following:

    • Base URL: https://sentry.io

    • Organization Slug: YOUR_ORG_SLUG

      • You can find your organization slug in the URL: https://sentry.io/organizations/YOUR_ORG_SLUG/
    • Email: Email

    Configuring Sentry in Okta

  5. Click "Save" to create the Sentry app.

  6. Click "Sign On" to the app settings page to which you are redirected. When the settings displayed in Step 5 appear, select "View Setup Instructions" in the bright yellow card to open a new tab.

  7. Copy the "Metadata URL" in the set up instructions.

    Okta metadata URL in setup instructions

  8. Sign in to Sentry. Select Settings > Auth > Configure Okta.

    Sentry single sign-on configuration page

  9. Paste the Metadata URL from Step 8, then click "Continue".

    Sentry single sign-on configuration for Okta

Sentry will attempt to authenticate and link your account with Okta. After successful authentication, you'll be redirected to Sentry's SSO configuration page, where you can:

  • Share the "Login URL" value, which will be used for SP-initiated SSO, with the users in your organization.

  • Scroll down to the bottom and ensure that "Require SSO" is checked if you want to enforce logging in with Okta.

  • Set a "Default Role" for new SSO users. Selecting "Member" should cover most use cases.

If you make any changes, click "Save Settings" to complete your set up.

Sentry single sign-on settings for Okta

Help improve this content
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").