HackerOne 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 HackerOne

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

Step 1: Set up Google as a SAML identity provider (IdP)
  1. Sign in to your Google Admin console.

    Sign in using an account with super administrator privileges (does not end in @gmail.com).

  2. In the Admin console, go to Menu and then Appsand thenWeb and mobile apps.
  3. Click Add appand thenSearch for apps.
  4. Enter HackerOne in the search field.
  5. In the search results, hover over the HackerOne SAML app and click Select
  6. On the Google Identity Provider details page:
    • Copy and save the SSO URL.
    • Download the Certificate.
  7. Click Continue.

    On the Service provider details page, the ACS URL and Entity ID values for HackerOne are configured by default.

  8. Click Continue.
  9. (Optional) On the Attribute Mapping page, map Google directory attributes to corresponding application attributes:
    1. Click Add Mapping.
    2. Click the Select field menu and select a Google directory attribute.
    3. Enter the corresponding application attribute under App attributes.
  10. (Optional) To enter group names that are relevant for this app:
    1. For Group membership (optional), click Search for a group, enter one or more letters of the group name, and select the group name.
    2. Add additional groups as needed (maximum of 75 groups).
    3. For App attribute, enter the service provider’s corresponding groups attribute name.

    Regardless of how many group names you enter, the SAML response will include only groups that a user is a member of (directly or indirectly). For more information, go to About group membership mapping.

  11. On the Attribute mapping page, click Finish.
Step 2: Enable the HackerOne app
  1. Sign in to your Google Admin console.

    Sign in using an account with super administrator privileges (does not end in @gmail.com).

  2. In the Admin console, go to Menu and then Appsand thenWeb and mobile apps.
  3. Select HackerOne.
  4. Click User access.
  5. To turn a service on or off for everyone in your organization, click On for everyone or Off for everyone, and then click Save.

  6. (Optional) To turn a service on or off for an organizational unit:
    1. At the left, select the organizational unit.
    2. To change the Service status, select On or Off.
    3. Choose one:
      • If the Service status is set to Inherited and you want to keep the updated setting, even if the parent setting changes, click Override.
      • If the Service status is set to Overridden, either click Inherit to revert to the same setting as its parent, or click Save to keep the new setting, even if the parent setting changes.
        Note: Learn more about organizational structure.
  7. (Optional) Turn on the service for a group of users.
    Use access groups to turn on a service for specific users within or across your organizational units. Learn more

  8. Ensure that your HackerOne user account email IDs match those in your Google domain.
Step 3: Set up HackerOne as a SAML 2.0 service provider (SP)

Note: HackerOne requires an X.509 certificate fingerprint, rather than an X.509 certificate. Before proceeding with the configuration steps below, use a conversion utility to convert the X.509 certificate generated in Step 1 into an X.509 certificate fingerprint. 

  1. Open a new incognito browser window.
  2. Sign in to https://hackerone.com/users/sign_in with your organization's HackerOne administrator account.
  3. Choose the HackerOne program in your account for which SSO needs to be enabled.
  4. Navigate to Settings > General > Authentication.
  5. In the SAML settings section, click Enable.
  6. Enter the following information in the respective fields:
    • your organization's email domain
    • the SSO URL copied in Step 1.
    • the converted X.509 certificate fingerprint (see Note above).

    After you enter your setup information, the Run test button is available to test single sign-on.

  7. Click Run test to verify your settings.

    After you successfully test your login settings, HackerOne will review and approve your SAML configuration and notify you within one day.

  8. Click Save.

    After you receive your SAML approval email from HackerOne, return to the Authentication Settings page and click Migrate Users to enable SSO for your users.

Step 4: Verify that the SSO is working

HackerOne supports both Identity Provider (IdP) initiated and Service Provider (SP) initiated SSO. Follow these steps to verify SSO in either mode:

IdP-initiated

  1. Sign in to your Google Admin console.

    Sign in using an account with super administrator privileges (does not end in @gmail.com).

  2. In the Admin console, go to Menu and then Appsand thenWeb and mobile apps.
  3. Select HackerOne.
  4. At the top left, click Test SAML login

    HackerOne should open in a separate tab. If it doesn’t, use the information in the resulting SAML error messages to update your IdP and SP settings as needed, then retest SAML login.

SP-initiated

  1. Close all browser windows.
  2. Open https://hackerone.com/users/sign_in and attempt to sign in, providing only your username. You should be automatically redirected to the Google sign in page.
  3. Enter your sign in credentials.
  4. After your sign in credentials are authenticated, you are automatically redirected back to HackerOne.
 


Google, Google Workspace, and related marks and logos are trademarks of Google LLC. All other company and product names are trademarks of the companies with which they are associated.

Was this helpful?

How can we improve it?
true
Search
Clear search
Close search
Google apps
Main menu
16085861702252334792
true
Search Help Center
true
true
true
false
false