Jenkins cloud application

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

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

Set up SSO via SAML for Jenkins

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  AppsWeb and mobile apps.
3. Click Add appSearch for apps.
4. Enter Jenkins in the search field.
5. In the search results, hover over the Jenkins SAML app and click Select. 
6. On the Google Identity Provider details page, download the IDP metadata.
7. Click Continue.
8. On the Service provider details page, 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 only include groups that a user is a member of (directly or indirectly). For more information, see About group membership mapping.

11. On the Attribute mapping page, click Finish.

Step 2: Set up Jenkins as a SAML 2.0 service provider (SP)

1. Open a new incognito browser window.
2. Sign in to https://wiki.jenkins.io/login.action with your organization's Jenkins administrator account.

3. Click on your account name. 

4. Click Manage Jenkins  Configure Global Security.

5. Check the Enable Security box.

6. Under the Security Realm section, select SAML 2.0.

7. In the IdP Metadata field, paste the content of the metadata you downloaded in Step 1.

8. At Authorization, select the appropriate option.

9. Click Save.

Step 3: Enable the Jenkins 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  AppsWeb and mobile apps.
3. Select Jenkins.
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 Jenkins user account email IDs match those in your Google domain.

Step 4: Verify that the SSO is working

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  AppsWeb and mobile apps.
3. Select Jenkins.
4. At the top left, click Test SAML login. 

   Jenkins 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.

 

_{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.}