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
@@ -133,8 +133,8 @@ Configure the BIG-IP registration to fulfill SAML tokens that BIG-IP APM request
133
133
134
134

135
135
136
-
> [!NOTE]
137
-
> Azure AD SAML signing certificates have a lifespan of three years.
136
+
> [!NOTE]
137
+
> Azure AD SAML signing certificates have a lifespan of three years.
138
138
139
139
Learn more: [Tutorial: Manage certificates for federated single sign-on](tutorial-manage-certificates-for-federated-single-sign-on.md)
140
140
@@ -155,157 +155,165 @@ Use the following instructions to configure BIG-IP.
155
155
156
156
SAML SP settings define the SAML SP properties that the APM will use for overlaying the legacy application with SAML pre-authentication. To configure them:
157
157
158
-
1. Select **Access** > **Federation** > **SAML Service Provider** > **Local SP Services**, and then select **Create**.
158
+
1. Select **Access** > **Federation** > **SAML Service Provider**.
159
+
2. Select **Local SP Services**.
160
+
3. Select **Create**.
159
161
160
-

162
+

161
163
162
-
1. On the **Create New SAML SP Service** pane, provide a name and the same entity ID that you defined earlier in Azure AD.
164
+
4. On the **Create New SAML SP Service** pane, for **Name**and **Entity ID**, enter the defined name and entity ID.
163
165
164
-

166
+

165
167
166
-
The values in the **SP Name Settings** section are required only if the entity ID isn't an exact match of the hostname portion of the published URL or, equally, if the entity ID isn't in regular hostname-based URL format. Provide the external scheme and hostname of the application that's being published if the entity ID is *urn:myvacation:contosoonline*.
168
+
> [!NOTE]
169
+
> **SP Name Settings** values are required if the entity ID doesn't match the hostname portion of the published URL. Or, values are required if the entity ID isn't in regular hostname-based URL format.
167
170
168
-
### Configure an external IdP connector
171
+
5. If the entity ID is `urn:myvacation:contosoonline`, enter the application external scheme and hostname.
169
172
170
-
A SAML IdP connector defines the settings that are required for the BIG-IP APM to trust Azure AD as its SAML IdP. These settings map the SAML service provider to a SAML IdP, which establishes the federation trust between the APM and Azure AD. To configure the connector:
173
+
### Configure an external IdPconnector
171
174
172
-
1. Select the new SAML service provider object, and then select **Bind/UnbBind IdP Connectors**.
175
+
A SAML IdP connector defines settings for the BIG-IP APM to trust Azure AD as its SAML IdP. The settings connect the SAML service provider to a SAML IdP, which establishes the federation trust between the APM and Azure AD.
173
176
174
-

177
+
To configure the connector:
175
178
176
-
1. In the **Create New IdP Connector** dropdown list, select **From Metadata**.
179
+
1. Select the new SAML service provider object.
180
+
2. Select **Bind/UnbBind IdP Connectors**.
177
181
178
-

179
-
180
-
1. On the **Create New SAML IdP Connector** pane, browse for the Federation Metadata XML file that you downloaded earlier, and then provide an **Identity Provider Name** for the APM object that will represent the external SAML IdP (for example, *MyVacation\_AzureAD*).
182
+

181
183
182
-

184
+
3. In the **Create New IdP Connector** list, select **From Metadata**.
183
185
184
-
1. Select **Add New Row** to choose the new **SAML IdP Connector**, and then select **Update**.
186
+

185
187
186
-

188
+
4. On the **Create New SAML IdP Connector** pane, browse for the Federation Metadata XML file you downloaded.
189
+
5. Enter an **Identity Provider Name** for the APM object that represents the external SAML IdP. For example, MyVacation\_AzureAD.
187
190
188
-
1.Select **OK** to save your settings.
191
+

189
192
190
-

193
+
6. Select **Add New Row**.
194
+
7. Select the new **SAML IdP Connector**.
195
+
8. Select **Update**.
196
+
197
+

191
198
192
-
### Configure Forms-based SSO
199
+
9. Select **OK**.
193
200
194
-
In this section, you create an APM SSO object for performing FBA SSO to back-end applications.
201
+

195
202
196
-
You can perform FBA SSO in either client-initiated mode or by the BIG-IP itself. Both methods emulate a user logon by injecting credentials into the username and password tags before auto submitting the form. The flow is almost transparent, except that users have to provide their password once when they access an FBA application. The password is then cached for reuse across other FBA applications.
203
+
### Configure forms-based SSO
197
204
198
-
This covers the APM approach, which manages SSO directly for the back-end application.
205
+
Create an APM SSO object for FBA SSO to back-end applications.
199
206
200
-
Select **Access** > **Single Sign-on** > **Forms Based**, select **Create**, and then provide the following values:
207
+
Perform FBA SSO in client-initiated mode or BIG-IP-initiated mode. Both methods emulate a user sign on by injecting credentials into the username and password tags. The form is then auto-submitted. Users provide password to access an FBA application. The password is cached and reused for other FBA applications.
201
208
202
-
|Property | Description |
203
-
|:------|:---------|
204
-
| Name | Use a descriptive name for the configuration, because an SSO APM object can be reused by other published applications. For example, use *Contoso\FBA\sso*.|
205
-
| Use SSO Template | None |
206
-
| Username Source | The preferred username source for pre-filling the password collection form. You can use any APM session variable, but the default *session.sso.token.last.username* tends to work best, because it contains the logged-in users' Azure AD UPN. |
207
-
| Password Source| Keep the default *session.sso.token.last.password*, it's the APM variable that the BIG-IP will use to cache the password that's provided by users. |
208
-
|||
209
+
1. Select **Access** > **Single Sign-on**.
210
+
2. Select **Forms Based**.
211
+
3. Select **Create**.
212
+
4. For **Name**, enter a descriptive name. For example, Contoso\FBA\sso.
213
+
5. For **Use SSO Template**, select **None**.
214
+
6. For **Username Source**, enter the username source to pre-fill the password collection form. The default `session.sso.token.last.username` works well, because it has the signed-in user Azure AD UPN.
215
+
7. For **Password Source**, keep the default `session.sso.token.last.password`, the APM variable BIG-IP uses to cache user passwords.
209
216
210
-

217
+

211
218
212
-
|Property | Description |
213
-
|:------|:---------|
214
-
| Start URI | The logon URI of your FBA application. The APM form-based authentication executes SSO when the request URI matches this URI value.|
215
-
| Form Actions | Leave this value blank so that the original request URL is used for SSO. |
216
-
| Form Parameter for Username | The element name of your logon form's username field. Use your browser's dev tools to determine this.|
217
-
| Form Parameter for Password | The element name of your logon form's password field. Use your browser's dev tools to determine this.|
218
-
|||
219
+
8. For **Start URI**, enter the FBA application logon URI. If the request URI matches this URI value, the APM form-based authentication executes SSO
220
+
9. For **Form Action**, leave it blank. Then, the original request URL is used for SSO.
221
+
10. For **Form Parameter for Username**, enter the logon form username field element. Use the browser dev tools to determine the element.
222
+
11. For **Form Parameter for Password**, enter the logon form password field element. Use the browser dev tools to determine the element.
219
223
220
-

224
+

221
225
222
-

226
+

223
227
224
-
For more information about configuring an APM for FBA SSO, go to the F5 [Single Sign-On Methods](https://techdocs.f5.com/en-us/bigip-14-1-0/big-ip-access-policy-manager-single-sign-on-concepts-configuration-14-1-0/single-sign-on-methods.html#GUID-F8588DF4-F395-4E44-881B-8D16EED91449) site.
228
+
To learn more, go to techdocs.f5.com for [Manual Chapter: Single Sign-On Methods](https://techdocs.f5.com/en-us/bigip-14-1-0/big-ip-access-policy-manager-single-sign-on-concepts-configuration-14-1-0/single-sign-on-methods.html#GUID-F8588DF4-F395-4E44-881B-8D16EED91449)
225
229
226
230
### Configure an Access profile
227
231
228
-
An access profile binds many APM elements managing access to BIG-IP virtual servers, including access policies, SSO configuration, and UI settings.
229
-
230
-
1. Select **Access** > **Profiles / Policies** > **Access Profiles (Per-Session Policies)** > **Create**, and then provide the following values:
232
+
An access profile binds APM elements that manage access to BIG-IP virtual servers, including access policies, SSO configuration, and UI settings.
231
233
232
-
| Property | Description |
233
-
|:-----|:-------|
234
-
| Name | For example, *MyVacation*|
235
-
|Profile Type | All |
236
-
| SSO Configuration | The FBA SSO configuration object you just created|
6. For **SSO Configuration**, select the FBA SSO configuration object you created.
240
+
7. For **Accepted Language**, select at least one language.
239
241
240
-

242
+

241
243
242
-
1. Modify the session policy to present a logon page with the username pre-filled. To launch the APM Visual Policy Editor, select the **Edit** link next to the per-session profile you just created.
244
+
8. In the **Per-Session Policy** column, for the profile, select **Edit**.

245
248
246
-
1. In the APM Visual Policy Editor, select the **+** sign next to the
247
-
fallback.
249
+
10. Under **fallback**, select the **+** sign.
248
250
249
-

251
+

250
252
251
-
1. In the pop-up window, select **Authentication**, select **SAML Auth**, and then select **Add Item**.
253
+
11. In the pop-up, select **Authentication**.
254
+
12. Select **SAML Auth**.
255
+
13. Select **Add Item**.
252
256
253
-

257
+

254
258
255
-
1. On the **SAML authentication SP** configuration pane, change the name to **Azure AD Auth** and then, in the **AAA Server** dropdown list, enter the SAML service provider object that you created earlier.
259
+
14. On **SAML authentication SP**, change the **Name** to **Azure AD Auth**
260
+
15. In the **AAA Server** dropdown, enter the SAML service provider object you created.
256
261
257
262

258
263
259
-
1. Select the **+** sign on the **Successful** branch.
260
-
261
-
1. In the pop-up window, select **Authentication**, select **Logon Page**, and then select **Add Item**.
1. In the **Read Only** column for the **username** field, in the dropdown list, select **Yes**.
266
-
267
-

264
+
16. On the **Successful** branch, select the **+** sign.
265
+
17. In the pop-up, select **Authentication**.
266
+
18. Select **Logon Page**
267
+
19. Select **Add Item**.
268
268
269
-
1. Add an SSO Credential Mapping object by selecting the plus sign (**+**) for the logon page fallback.
269
+

270
270
271
-
1. In the pop-up window, select the **Assignment** tab, select **SSO Credential Mapping**, and then select **Add Item**.
271
+
20. For **usesrname**, in the **Read Only** column, select **Yes**.
272
272
273
-

273
+

274
274
275
-
1. On the **Variable Assign: SSO Credential Mapping** pane, keep the default settings, and then select **Save**.
275
+
21. For the logon page fallback, select the **+** sign. This action adds an SSO credential mapping object.
276
276
277
-

277
+
22. In the pop-up, select the **Assignment** tab.
278
+
23. Select **SSO Credential Mapping**.
279
+
24. Select **Add Item**.
278
280
279
-
1. Select the link in the upper **Deny** box to change the **Successful** branch to **Allow**, and then select **Save**.
281
+

280
282
281
-
**(Optional) Configure attribute mappings**
283
+
25. On **Variable Assign: SSO Credential Mapping**, keep the default settings.
284
+
26. Select **Save**.
282
285
283
-
Although it's optional, adding a LogonID_Mapping configuration enables the BIG-IP active sessions list to display the UPN of the logged-in user instead of a session number. This information is useful when you're analyzing logs or troubleshooting.
286
+

284
287
285
-
1. Select the plus (**+**) symbol for the **SAML Auth Successful** branch.
288
+
27. In the upper **Deny** box, select the link.
289
+
28. The **Successful** branch changes to **Allow**
290
+
29. Select **Save**.
286
291
287
-
1. In the pop-up dialog, select **Assignment** > **Variable Assign** > **Add Item**.
292
+
#### (Optional) configure attribute mappings
288
293
289
-

294
+
You can add a LogonID_Mapping configuration. Then, the BIG-IP active sessions list has the signed-in user UPN, not a session number. Use this information for analyzing logs or troubleshooting.
290
295
291
-
1. On the **Properties** pane, enter a descriptive name (for example,
292
-
*LogonID_Mapping*) and, under **Variable Assign**, select **Add new entry** > **change**.
296
+
1. For the **SAML Auth Successful** branch, select the **+** sign.
297
+
2. In the pop-up, select **Assignment**.
298
+
3. Select **Variable Assign**.
299
+
4. Select **Add Item**.
293
300
294
-

301
+

295
302
296
-
1. Set both variables:
297
-
298
-
| Property | Description |
299
-
|:-----|:-------|
300
-
| Custom Variable |`session.logon.last.username`|
301
-
| Session Variable |`session.saml.last.identity`|
302
-
|||
303
+
1. On the **Properties** tab, enter a **Name**. For example, LogonID_Mapping.
304
+
2. Under **Variable Assign**, select **Add new entry**
305
+
3. Select **change**.
303
306
304
-
1. Select **Finished** > **Save**.
307
+

305
308
306
-
1. Commit those settings by selecting **Apply Access Policy** and then close the Visual Policy Editor.
309
+
4. For **Custom Variable**, use `session.logon.last.username`.
310
+
5. For Session Variable, user `session.saml.last.identity`.
311
+
6. Select **Finished**.
312
+
7. Select **Save**.
313
+
8. Select **Apply Access Policy**.
314
+
9. Close the Visual Policy Editor.
307
315
308
-

316
+

0 commit comments