Jenkins SAML SSO app gives the ability to enable SAML Single Sign-On (SSO) for Jenkins. Here we will go through a guide to configure Single Sign On (SSO) between Jenkins and Okta. By the end of this guide, Okta users should be able to log in and register to Jenkins.
To integrate your Identity Provider (IDP) with Jenkins, you need the following items:
With the plugin installed, you can move on to setting up Okta as an IDP.
1.1: Okta IDP Configuration
Follow the steps provided below:
Single Sign On URL | Enter ACS (Assertion Consumer Service) URL from the Service Provider info tab of the plugin. |
Audience URI (SP Entity ID) | Enter SP Entity ID/Issuer from the Service Provider info (or SP Information) tab of the module. |
Default Relay State | Enter Relay State from the Service Provider info tab of the module. |
Name ID Format | Select EmailAddress as the Name ID Format from the dropdown list. |
Application Username | Set Application Username to Okta username. |
a. For Name, enter "firstName" and select user.firstName from the value dropdown.
b. For Name, enter "lastName" and select user.lastName from the value dropdown.
c. For Name, enter "Email" and select user.email from the value dropdown.
d. Under Group Attribute Statements, enter "groups" for Name and select Matches regex from the Filter dropdown and enter ".*" in the adjacent textbox.
1.2: Assigning Groups/People
1.3: Fetching Metadata URL
One important component you’ll require while setting up your service provider is the metadata URL of your Identity Provider.
You can follow these steps to find the metadata URL for your Okta Application:
If you don't find what you are looking for, please contact us at support-atlassian@miniorange.atlassian.net or raise a support ticket here.