You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -55,7 +55,6 @@ To configure the integration of EasySSO for Jira into Azure AD, you need to add
55
55
1. In the **Add from the gallery** section, type **EasySSO for Jira** in the search box.
56
56
1. Select **EasySSO for Jira** from results panel and then add the app. Wait a few seconds while the app is added to your tenant.
57
57
58
-
59
58
## Configure and test Azure AD single sign-on for EasySSO for Jira
60
59
61
60
Configure and test Azure AD SSO with EasySSO for Jira using a test user called **B.Simon**. For SSO to work, you need to establish a link relationship between an Azure AD user and the related user in EasySSO for Jira.
@@ -144,13 +143,50 @@ In this section, you'll enable B.Simon to use Azure single sign-on by granting a
144
143
145
144
## Configure EasySSO for Jira SSO
146
145
147
-
To configure single sign-on on **EasySSO for Jira** side, you need to send the **App Federation Metadata Url** to [EasySSO for Jira support team](mailto:[email protected]). They set this setting to have the SAML SSO connection set properly on both sides.
146
+
1. Sign into your Atlassian Jira instance with Administrator privileges and navigate to the **Manage Apps** section.
1. Select **Certificates** tab on the top and you will be presented with the following screen and locate **Certificate (Base64)** or **Metadata File** you have saved in the earlier steps of **Azure AD SSO** configuration. You have following options on how to proceed:
a. Use the App Federation **Metadata File** you downloaded to local file on your computer. Select **Upload** radio button and follow the upload file dialog specific to your operating system
163
+
164
+
**OR**
165
+
166
+
b. Open the App Federation **Metadata File** to see the content (in any plain text editor) of the file and copy it into the clipboard. Select **Input** option and paste clipboard content into the text field.
167
+
168
+
**OR**
169
+
170
+
c. Fully manual configuration. Open the App Federation **Certificate (Base64)** to see the content (in any plain text editor) of the file and copy it into the clipboard. Paste it into **IdP Token Signing Certificates** text field. Then navigate to **General** tab and fill **POST Binding URL** and **Entity ID** fields with respective values for **Login URL** and **Azure AD Identifier** you saved previously.
171
+
172
+
1. Click **Save** button on the bottom of the page. You will see the content of the Metadata or Certificate files is parsed into the configuration fields. EasySSO for Jira configuration is complete.
173
+
174
+
1. For the best testing experience, navigate to **Look & Feel** tab and check the **SAML Login Button** option on. This will enable separate button on the Jira login screen specifically to test your Azure AD SAML integration end to end. You can leave this button on and configure its placement, colour and translation for production mode, too.
> Should you have any issues, please contact [EasySSO support team](mailto:[email protected]).
148
180
149
181
### Create EasySSO for Jira test user
150
182
151
-
In this section, a user called Britta Simon is created in EasySSO for Jira. EasySSO for Jira supports just-in-time user provisioning, which is enabled by default. There is no action item for you in this section. If a user doesn't already exist in EasySSO for Jira, a new one is created after authentication.
183
+
In this section, a user called B.Simon is created in Jira. EasySSO for Jira supports just-in-time user provisioning, which is **disabled** by default. To enable user provisioning, you have to explicitly check **Create user on successful login** option on in the General section of EasySSO plugin configuration. If a user doesn't already exist in Jira, a new one is created after authentication.
184
+
185
+
However, if you do not wish to enable automatic user provisioning on the user first login, users must exist in backend User Directories the Jira instance make use of, such as LDAP or Atlassian Crowd.
0 commit comments