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/saas-apps/headerf5-tutorial.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
@@ -14,7 +14,7 @@ ms.workload: identity
14
14
ms.tgt_pltfrm: na
15
15
ms.devlang: na
16
16
ms.topic: tutorial
17
-
ms.date: 11/01/2019
17
+
ms.date: 11/19/2019
18
18
ms.author: jeedes
19
19
20
20
ms.collection: M365-identity-device-management
@@ -34,11 +34,11 @@ To learn more about SaaS app integration with Azure AD, see [What is application
34
34
35
35
To get started, you need the following items:
36
36
37
-
1. An Azure AD subscription. If you don't have a subscription, you can get a [free account](https://azure.microsoft.com/free/).
37
+
* An Azure AD subscription. If you don't have a subscription, you can get a [free account](https://azure.microsoft.com/free/).
38
38
39
-
1. F5 single sign-on (SSO) enabled subscription.
39
+
* F5 single sign-on (SSO) enabled subscription.
40
40
41
-
1. Deploying the joint solution requires the following license:
41
+
* Deploying the joint solution requires the following license:
42
42
43
43
* F5 BIG-IP® Best bundle (or)
44
44
@@ -54,36 +54,36 @@ To get started, you need the following items:
54
54
55
55
* A network hardware security module (HSM) to safeguard and manage digital keys for strong authentication
56
56
57
-
2. F5 BIG-IP system is provisioned with APM modules (LTM is optional)
57
+
*F5 BIG-IP system is provisioned with APM modules (LTM is optional)
58
58
59
-
3. Although optional, it is highly recommended to Deploy the F5 systems in a [sync/failover device group](https://techdocs.f5.com/content/techdocs/en-us/bigip-14-1-0/big-ip-device-service-clustering-administration-14-1-0.html) (S/F DG), which includes the active standby pair, with a floating IP address for high availability (HA). Further interface redundancy can be achieved using the Link Aggregation Control Protocol (LACP). LACP manages the connected physical interfaces as a single virtual interface (aggregate group) and detects any interface failures within the group.
59
+
*Although optional, it is highly recommended to Deploy the F5 systems in a [sync/failover device group](https://techdocs.f5.com/content/techdocs/en-us/bigip-14-1-0/big-ip-device-service-clustering-administration-14-1-0.html) (S/F DG), which includes the active standby pair, with a floating IP address for high availability (HA). Further interface redundancy can be achieved using the Link Aggregation Control Protocol (LACP). LACP manages the connected physical interfaces as a single virtual interface (aggregate group) and detects any interface failures within the group.
60
60
61
-
4. For Kerberos applications, an on-premises AD service account for constrained delegation. Refer to [F5 Documentation](https://support.f5.com/csp/article/K43063049) for creating a AD delegation account.
61
+
* For Kerberos applications, an on-premises AD service account for constrained delegation. Refer to [F5 Documentation](https://support.f5.com/csp/article/K43063049) for creating a AD delegation account.
62
62
63
63
## Access guided configuration
64
64
65
-
1. Access guided configuration’ is supported on F5 TMOS version 13.1.0.8 and above. If your BIG-IP system is running a version below 13.1.0.8, please refer to the **Advanced configuration** section.
65
+
* Access guided configuration’ is supported on F5 TMOS version 13.1.0.8 and above. If your BIG-IP system is running a version below 13.1.0.8, please refer to the **Advanced configuration** section.
66
66
67
-
1. Access guided configuration presents a completely new and streamlined user experience. This workflow-based architecture provides intuitive, re-entrant configuration steps tailored to the selected topology.
67
+
* Access guided configuration presents a completely new and streamlined user experience. This workflow-based architecture provides intuitive, re-entrant configuration steps tailored to the selected topology.
68
68
69
-
1. Before proceeding to the configuration, upgrade the guided configuration by downloading the latest use case pack from [downloads.f5.com](https://login.f5.com/resource/login.jsp?ctx=719748). To upgrade, follow the below procedure.
69
+
* Before proceeding to the configuration, upgrade the guided configuration by downloading the latest use case pack from [downloads.f5.com](https://login.f5.com/resource/login.jsp?ctx=719748). To upgrade, follow the below procedure.
70
70
71
71
>[!NOTE]
72
72
>The screenshots below are for the latest released version (BIG-IP 15.0 with AGC version 5.0). The configuration steps below are valid for this use case across from 13.1.0.8 to the latest BIG-IP version.
73
73
74
-
* On the F5 BIG-IP Web UI, click on Access >> Guide Configuration.
74
+
1. On the F5 BIG-IP Web UI, click on **Access >> Guide Configuration**.
75
75
76
-
* On the **Guided Configuration** page, click on **Upgrade Guided Configuration** on the top left-hand corner.
76
+
1. On the **Guided Configuration** page, click on **Upgrade Guided Configuration** on the top left-hand corner.
* On the Upgrade Guide Configuration pop screen, select **Choose File** to upload the downloaded use case pack and click on **Upload and Install** button.
80
+
1. On the Upgrade Guide Configuration pop screen, select **Choose File** to upload the downloaded use case pack and click on **Upload and Install** button.
@@ -99,17 +99,17 @@ In this tutorial, you configure and test Azure AD SSO in a test environment.
99
99
100
100
### Key Authentication Scenarios
101
101
102
-
Apart from Azure Active Directory native integration support for modern authentication protocols like Open ID Connect, SAML and WS-Fed, F5 extends secure access for legacy-based authentication apps for both internal and external access with Azure AD, enabling modern scenarios (e.g. password-less access) to these applications. This include:
102
+
*Apart from Azure Active Directory native integration support for modern authentication protocols like Open ID Connect, SAML and WS-Fed, F5 extends secure access for legacy-based authentication apps for both internal and external access with Azure AD, enabling modern scenarios (e.g. password-less access) to these applications. This include:
103
103
104
-
Header-based authentication apps
104
+
*Header-based authentication apps
105
105
106
-
Kerberos authentication apps
106
+
*Kerberos authentication apps
107
107
108
-
Anonymous authentication or no inbuilt authentication apps
108
+
*Anonymous authentication or no inbuilt authentication apps
109
109
110
-
NTLM authentication apps (protection with dual prompts for the user)
110
+
*NTLM authentication apps (protection with dual prompts for the user)
111
111
112
-
Forms Based Application (protection with dual prompts for the user)
112
+
*Forms Based Application (protection with dual prompts for the user)
113
113
114
114
## Adding F5 from the gallery
115
115
@@ -231,11 +231,11 @@ In this section, you'll enable B.Simon to use Azure single sign-on by granting a
1. Provide a **Configuration Name**. Specify the **Entity ID** (same as what you configured on the Azure AD Application Configuration). Specify the **Host name**. Add a **Description** for reference.Accept the remaining default entries and select and then click **Save & Next**.
234
+
1. Provide a **Configuration Name**. Specify the **Entity ID** (same as what you configured on the Azure AD Application Configuration). Specify the **Host name**. Add a **Description** for reference.Accept the remaining default entries and select and then click **Save & Next**.
1. In this example we are creating a new Virtual Server as 192.168.30.20 with port 443.Specify the Virtual Server IP address in the **Destination Address**. Select the Client **SSL Profile**, select Create new. Specify previously uploaded application certificate, (the wild card certificate in this example) and the associated key, and then click **Save & Next**.
238
+
1. In this example we are creating a new Virtual Server as 192.168.30.20 with port 443.Specify the Virtual Server IP address in the **Destination Address**. Select the Client **SSL Profile**, select Create new. Specify previously uploaded application certificate, (the wild card certificate in this example) and the associated key, and then click **Save & Next**.
239
239
240
240
>[!NOTE]
241
241
>in this example our Internal webserver is running on port 888 and we want to publish it with 443.
@@ -252,11 +252,11 @@ In this section, you'll enable B.Simon to use Azure single sign-on by granting a
252
252
253
253
1. On the Single Sign-On Settings screen, select **Enable Single Sign-On**. Under Selected Single Sign-On Type choose **HTTP header-based**. Replace **session.saml.last.Identity** with **session.saml.last.attr.name.Identity** under Username Source ( this variable it set using claims mapping in the Azure AD ). Under SSO Headers.
254
254
255
-
o **HeaderName : MyAuthorization**
255
+
* **HeaderName : MyAuthorization**
256
256
257
-
o **Header Value : %{session.saml.last.attr.name.Identity}**
257
+
* **Header Value : %{session.saml.last.attr.name.Identity}**
258
258
259
-
o Click **Save & Next**
259
+
* Click **Save & Next**
260
260
261
261
Refer Appendix for complete list of variables and values. You can add more headers as required.
0 commit comments