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
Copy file name to clipboardExpand all lines: articles/active-directory/manage-apps/f5-aad-password-less-vpn.md
+28-28Lines changed: 28 additions & 28 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,7 +37,7 @@ To learn about more benefits, see
37
37
38
38
In this scenario, the BIG-IP APM instance of the SSL-VPN service is configured as a SAML service provider (SP) and Azure AD is the trusted SAML IDP. SSO from Azure AD is provided through claims-based authentication to the BIG-IP APM, a seamless VPN access experience.
>Replace example strings or values in this guide with those in your environment.
@@ -100,11 +100,11 @@ Set up a SAML federation trust between the BIG-IP to allow the Azure AD BIG-IP t
100
100
10. Skip the SSO test prompt.
101
101
11. In **User Attributes & Claims** properties, observe the details.
102
102
103
-

103
+

104
104
105
105
You can add other claims to your BIG-IP published service. Claims defined in addition to the default set are issued if they're in Azure AD. Define directory [roles or group](../hybrid/how-to-connect-fed-group-claims.md) memberships against a user object in Azure AD, before they can be issued as a claim.
SAML signing certificates created by Azure AD have a lifespan of three years.
110
110
@@ -118,7 +118,7 @@ By default, Azure AD issues tokens to users with granted access to a service.
118
118
4. In the **Users and groups** dialog, add the user groups authorized to access the VPN
119
119
5. Select **Select** > **Assign**.
120
120
121
-

121
+

122
122
123
123
You can set up BIG-IP APM to publish the SSL-VPN service. Configure it with corresponding properties to complete the trust for SAML pre-authentication.
124
124
@@ -131,36 +131,36 @@ To complete federating the VPN service with Azure AD, create the BIG-IP SAML ser
131
131
1. Go to **Access** > **Federation** > **SAML Service Provider** > **Local SP Services**.
3. Enter a **Name** and the **Entity ID** defined in Azure AD.
137
137
4. Enter the Host FQDN to connect to the application.
138
138
139
-

139
+

140
140
141
141
>[!NOTE]
142
142
>If the entity ID isn't an exact match of the hostname of the published URL, configure SP **Name** settings, or perform this action if it isn’t in hostname URL format. If entity ID is `urn:ssl-vpn:contosoonline`, provide the external scheme and hostname of the application being published.
143
143
144
144
5. Scroll down to select the new **SAML SP object**.
145
145
6. Select **Bind/UnBind IDP Connectors**.
146
146
147
-

147
+

148
148
149
149
7. Select **Create New IDP Connector**.
150
150
8. From the drop-down menu, select **From Metadata**
151
151
152
-

152
+

153
153
154
154
9. Browse to the federation metadata XML file you downloaded.
155
155
10. For the APM object,provide an **Identity Provider Name** that represents the external SAML IdP.
156
156
11. To select the new Azure AD external IdP connector, select **Add New Row**.
>See the F5 article, [Configuring Network Access Resources](https://techdocs.f5.com/kb/en-us/products/big-ip_apm/manuals/product/apm-network-access-11-5-0/2.html) for other settings.
@@ -224,7 +224,7 @@ A BIG-IP connection profile is required to configure VPN client-type settings th
224
224
3. Enter a profile name.
225
225
4. Set the parent profile to **/Common/connectivity**, for example, Contoso_VPN_Profile.
226
226
227
-

227
+

228
228
229
229
For more information on client support, see the F5 article, [F5 Access and BIG-IP Edge Client](https://techdocs.f5.com/kb/en-us/bigip-edge-apps.html).
230
230
@@ -239,51 +239,51 @@ An access policy enables the service for SAML authentication.
239
239
5. Scroll down and add at least one language to the **Accepted Languages** list
240
240
6. Select **Finished**.
241
241
242
-

242
+

243
243
244
244
7. In the new access profile, on the Per-Session Policy field, select **Edit**.
>Select the VPN tile to install the BIG-IP Edge client and establish a VPN connection configured for SHA. The F5 VPN application is visible as a target resource in Azure AD Conditional Access. See [conditional access policies](../conditional-access/concept-conditional-access-policies.md) to enable users for Azure AD [password-less authentication](https://www.microsoft.com/security/business/identity/passwordless).
0 commit comments