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

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. From the Admin console Home page, go to Appsand thenWeb and mobile apps.
  3. Click Add appand thenSearch for apps.
  4. Enter Buildkite in the search field.
  5. In the search results, hover over the Buildkite SAML app and click Select.
  6. On the Google Identity Provider details page:
    • Copy and save the SSO URL and Entity ID.
    • Download the Certificate.
  7. Click Continue.
  8. On the Service provider details page, edit the ACS URL,  replacing {org_name} with your organization’s name as set up on Buildkite.
  9. Click Continue.

    Note: Attribute mapping is not required for Buildkite.

  10. On the Attribute mapping page, click Finish.
Step 2: Set up Buildkite as a SAML 2.0 service provider (SP)
  1. Send an email to Buildkite support asking them to enable SSO for your account. Include your organization’s email domain and the following information you copied from Google in Step 1 above:
    • SSO URL.
    • Certificate (attached as a text file).

    Once Buildkite has set up SSO for your account, you can sign in to Buildkite to verify that it’s enabled.

  2. Sign in to your Buildkite account as administrator.
  3. Click on Settings and then Single Sign-On.

    You should see a message verifying that SSO is enabled and showing the login URL for your organization.

Step 3: Enable the Buildkite 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. From the Admin console Home page, go to Appsand thenWeb and mobile apps.
  3. Select Buildkite.
  4. Click User access.
  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. (Optional) To turn a service on or off for an organizational unit:

    1. At the left, select the organizational unit.
    2. Select On or Off.
    3. Click Override to keep your setting if the service for the parent organizational unit is changed.
    4. If Overridden is already set for the organizational unit, 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. (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 Buildkite user account email IDs match those in your Google domain.
Step 4: Verify that the SSO is working

Buildkite 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. From the Admin console Home page, go to Appsand thenWeb and mobile apps.
  3. Select Buildkite.
  4. At the top left, click Test SAML login

    Buildkite 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://buildkite.com/login?org={org_name} and attempt to sign in. You should be automatically redirected to the Google sign-in page.
  3. Enter your sign-in credentials.

    After your sign-in credentials are authenticated you're automatically redirected back to Buildkite.



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?