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
@@ -99,7 +99,7 @@ Follow these steps to enable Azure AD SSO in the Azure portal.
99
99

100
100
101
101
1. In addition to above, EasySSO for Bamboo application expects few more attributes to be passed back in SAML response which are shown below. These attributes are also pre populated but you can review them as per your requirements.
@@ -144,13 +144,50 @@ In this section, you'll enable B.Simon to use Azure single sign-on by granting a
144
144
145
145
## Configure EasySSO for Bamboo SSO
146
146
147
-
To configure single sign-on on **EasySSO for Bamboo** side, you need to send the **App Federation Metadata Url** to [EasySSO for Bamboo support team](mailto:[email protected]). They set this setting to have the SAML SSO connection set properly on both sides.
147
+
1. Sign into your EasySSO for Bamboo instance with Administrator privileges and navigate to the **Manage Apps** section.
148
+
149
+

150
+
151
+
1. Click on **EasySSO**.
152
+
153
+

154
+
155
+
1. Select **SAML** option. This will take you to SAML configuration section.
156
+
157
+

158
+
159
+
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:
160
+
161
+

162
+
163
+
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
164
+
165
+
**OR**
166
+
167
+
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.
168
+
169
+
**OR**
170
+
171
+
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.
172
+
173
+
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 Bamboo configuration is complete.
174
+
175
+
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 EasySSO for Bamboo login screen specifically to test your Azure AD SAML integration end to end. You can leave this button on and configure its placement, color and translation for production mode, too.
176
+
177
+

178
+
179
+
> [!NOTE]
180
+
> Should you have any issues, please contact [EasySSO support team](mailto:[email protected]).
148
181
149
182
### Create EasySSO for Bamboo test user
150
183
151
-
In this section, a user called Britta Simon is created in EasySSO for Bamboo. EasySSO for Bamboo 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 Bamboo, a new one is created after authentication.
184
+
In this section, a user called B.Simon is created in EasySSO for Bamboo. EasySSO for Bamboo 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 EasySSO for Bamboo, a new one is created after authentication.
185
+
186
+
However, if you do not wish to enable automatic user provisioning on the user first login, users must exist in backend User Directories the EasySSO for Bamboo instance make use of, such as LDAP or Atlassian Crowd.
0 commit comments