Skip to content

Commit 446accb

Browse files
authored
Update f5-big-ip-headers-easy-button.md
1 parent 3d94540 commit 446accb

File tree

1 file changed

+12
-14
lines changed

1 file changed

+12
-14
lines changed

articles/active-directory/manage-apps/f5-big-ip-headers-easy-button.md

Lines changed: 12 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -43,26 +43,24 @@ A BIG-IP in front of the application enables uoverlay of the service with Azure
4343

4444
The SHA solution contains:
4545

46-
* **Application** - BIG-IP published service to be protected by Azure AD SHA.
47-
* **Azure AD** - Security Assertion Markup Language (SAML) Identity Provider (IdP) responsible for verification of user credentials, Conditional Access (CA), and SAML based SSO to the BIG-IP. Through SSO, Azure AD provides the BIG-IP with any required session attributes.
48-
* **BIG-IP** - reverse proxy and SAML service provider (SP) to the application, delegating authentication to the SAML IdP before performing header-based SSO to the backend application.
46+
* **Application** - BIG-IP published service protected by Azure AD SHA
47+
* **Azure AD** - Security Assertion Markup Language (SAML) identity provider (IdP) that verifies user credentials, Conditional Access, and SAML-based SSO to the BIG-IP. With SSO, Azure AD provides the BIG-IP with session attributes.
48+
* **BIG-IP** - reverse-proxy and SAML service provider (SP) to the application, delegating authentication to the SAML IdP before performing header-based SSO to the backend application.
4949

50-
SHA for this scenario supports both SP and IdP initiated flows. The following image illustrates the SP initiated flow.
50+
For this scenario, SHA supports SP- and IdP-initiated flows. The following diagram illustrates the SP-initiated flow.
5151

52-
![Secure hybrid access - SP initiated flow](./media/f5-big-ip-easy-button-header/sp-initiated-flow.png)
52+
![Diagram of the configuration with an SP-initiated flow.](./media/f5-big-ip-easy-button-header/sp-initiated-flow.png)
5353

54-
| Steps| Description |
55-
| - |----|
56-
| 1| User connects to application endpoint (BIG-IP) |
57-
| 2| BIG-IP APM access policy redirects user to Azure AD (SAML IdP) |
58-
| 3| Azure AD pre-authenticates user and applies any enforced Conditional Access policies |
59-
| 4| User is redirected to BIG-IP (SAML SP) and SSO is performed using issued SAML token |
60-
| 5| BIG-IP injects Azure AD attributes as headers in request to the application |
61-
| 6| Application authorizes request and returns payload |
54+
1. User connects to application endpoint (BIG-IP).
55+
2. BIG-IP APM access policy redirects user to Azure AD (SAML IdP).
56+
3. Azure AD preauthenticates user and applies Conditional Access policies.
57+
4. User is redirected to BIG-IP (SAML SP) and SSO occurs using issued SAML token.
58+
5. BIG-IP injects Azure AD attributes as headers in application request.
59+
6. Application authorizes request and returns payload.
6260

6361
## Prerequisites
6462

65-
Prior BIG-IP experience isn’t necessary, but you’ll need:
63+
For the scenario you need:
6664

6765
* An Azure AD free subscription or above
6866

0 commit comments

Comments
 (0)