Sentry cloud application

You must be signed in as a super administrator for this task.

Using Security Assertion Markup Language (SAML), your users can use their Google Cloud credentials to sign in to enterprise-cloud applications.

Set up SSO via SAML for Sentry

Here's how to set up single sign-on (SSO) via SAML for the Sentry® application.

Step 1: Get Google identity provider (IdP) information
  1. Sign in to your Google Admin console.

    Sign in using your administrator account (does not end in @gmail.com).

  2. From the Admin console Home page, go to Security, and then the SSO settings:

    You must be signed in as a super administrator for this task.

    Click Set up single sign-on (SSO) for SAML applications.

    Or, if you don’t have that option:

    Click Set up single sign-on (SSO).

  3. In the Set up single sign-on (SSO) section:
    1. Copy and save the SSO URL.
    2. Copy and save the Entity ID.
    3. Download the Certificate.

In the next step, you send this information to Sentry via email. After they respond, you return to the Admin console in Step 3 below to finish SSO configuration.

Step 2: Send IdP information to Sentry

Email Sentry Support (compliance@sentry.io) and request that they enable SSO for your account. Include the following identity provider (IdP) information copied in Step 1:

  • SSO URL 
  • Entity ID 
  • Attach the certificate you downloaded in Step 1 as a text file attachment to the email.

Sentry will process your request and provide you with ACS URL and Entity ID values. Use these values to finish configuring SSO in the Admin console in Step 3 below.

Step 3: Finish SSO configuration in Admin console
  1. Sign in to your Google Admin console.

    Sign in using your administrator account (does not end in @gmail.com).

  2. From the Admin console Home page, go to Apps and then SAML apps.

    To see Apps on the Home page, you might have to click More controls at the bottom. 

  3. Click Add Add at bottom right.
  4. Locate and click Sentry in the application list.
  5. Click Next.

    The Basic information window shows the Application name and Description seen by users.

  6. Click Next.
  7. On the Service Provider Details page, replace the default ACS URL and Entity ID values with the ACS URL and Entity ID values received from Sentry Support.
  8. Click Next.
  9. On the Attribute Mapping page, set the Select category and Select user field values as follows for the listed attributes:
     
    Application attribute Select category Select user field
    Emailaddress Basic Information Primary Email
  10. Click Finish.
Step 4: Enable the Sentry app
  1. Sign in to your Google Admin console.

    Sign in using your administrator account (does not end in @gmail.com).

  2. From the Admin console Home page, go to Apps and then SAML apps.

    To see Apps on the Home page, you might have to click More controls at the bottom. 

  3. Select Sentry.
  4. At the top right of the gray box, click Edit Service Compose.

  5. To turn on or off a service for everyone in your organization, click On for everyone or Off for everyone, and then click Save.

  6. To turn on or off a service only for users in an organizational unit:

    1. At the left, select the organizational unit.
    2. Select On or Off.
    3. To keep the service turned on or off even when the service is turned on or off for the parent organizational unit, click Override.
    4. If the organization's status is already Overridden, choose an option:
      • Inherit—Reverts to the same setting as its parent.
      • Save—Saves your new setting (even if the parent setting changes).

    Learn more about organizational structure.

  7. Ensure that your Sentry user account email IDs match those in your Google domain.
Step 5: Verify that the SSO is working
  1. Open https://sentry.io/auth/login/{your_unique_organization_ID}/. You should be automatically redirected to the Google sign-in page.
  2. Enter your username and password.

After your sign in credentials are authenticated, you're automatically redirected back to Sentry.

Was this helpful?
How can we improve it?