Buildkite - SAML Relying Party Configuration - RSA Ready SecurID Access Implementation Guide

This section describes how to integrate RSA SecurID Access with Buildkite using Relying Party. Relying party uses SAML 2.0 to integrate RSA SecurID Access as a SAML Identity Provider (IdP) to Buildkite SAML Service Provider (SP).

Architecture Diagram

Configure RSA Cloud Authentication Service

Perform these steps to configure RSA Cloud Authentication Service as a relying party SAML IdP to Buildkite .

Procedure

1. Sign into the RSA Cloud Administration Console and browse to Authentication Clients > Relying Parties and click Add a Relying Party.

1. On Basic Information page enter a Name for the application, ie. Buildkite Then click on Next Step.

2. On Authentication page.

   1. select the RSA SecurID Access manages all authentication.

   2. Select the desired Primary Authentication Method from the dropdown list.

   3. Select the desired policy from the Access Policy for Additional Authentication.

   4. Click Next Step.

   

    

3. On Connection Profile page.

   1. Enter the Assertion Consumer Service (ACS) . This is the ACS URL found in your instance of Buildkite . For example https://buildkite.com/sso/~/[ACCOUNT NAME]/saml/consume.

   2. Enter the Service Provider Entity ID. This is the Issuer (Entity ID) found in your instance of Buildkite . For example https://buildkite.com.

   3. Click on Download Certificate. This will be used below in the Buildkite configuration.

   4. Click on Choose File and upload the certificate just downloaded.  This same certificate will be used in the Buildkite configuration below.

   5. Open Advanced Configuration section and note the Identity Provider Entity ID field . For Example :https://rsa-blr-pe.auth-demo.securid.com/saml-fe/sso.

   6. Click on Save and Finish.

   

4. Browse to Authentication Clients > Relying Parties

5. Scroll down to the your newly created Relying party and click down arrow to Edit and choose View or Download IdP MetatData if you want to save off the metadata information.

1. Click on Publish Changes. Your application is now enabled for SSO. If you make any additional changes to the application configuration you will need to republish.

   

    

Configure Buildkite

Perform these steps to integrate Buildkite with RSA SecurID Access as a Relying Party SAML SP.

Procedure

1. Sign into Buildkite and browse to Settings > Single Sign On > Custom SAML.

2. Click on  Configure IdP Metadata Manually.

3. In the Service Provider section note the Issuer (Entity ID), Assertion Consumer Service URL, and Meda Data URL, they may be used above to configure the SecurID Cloud Authentication Service above.

4. For SAML Target URL, enter the Identity Provider Entity ID from the RSA CAS configuration above. For example, https://rsa-blr-pe.auth-demo.securid.com/saml-fe/sso.

5. For Enitity ID, enter the Identity Provider Entity ID from the RSA CAS configuration above. For example, https://rsa-blr-pe.auth-demo.securid.com/saml-fe/sso.

6. For the Certificate paste the contents of downloaded certificate from step 4c in the RSA CAS configuration above.

7. Click on Save Settings.

8. Click on Perform Test Login.

9. Click on Enable Provider.

Configuration is complete.

Next Step: See main page for more certification information.