Skip to content

Commit e96d450

Browse files
Victor LeeVictor Lee
authored andcommitted
DOC-2458-adminportal-sso-auth-context
1 parent a9860dd commit e96d450

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

modules/admin-portal/pages/security/sso-aad.adoc

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,11 @@ First, use the xref:security/sso.adoc[SSO documentation] to set up SSO in Admin
4141
Next, follow these steps:
4242

4343
. Enter the Identity Provider's Entity ID and Identity Provider SSO URL you copied in Step 9 of the previous section.
44-
. At the bottom of the screen, for the *Authentication Context* section, use `urn:oasis:names:tc:SAML:2.0:ac:classes:Password`
44+
. At the bottom of the screen, for the *Authentication Context* section, if SSO should always be authenticated by password, use `urn:oasis:names:tc:SAML:2.0:ac:classes:Password`
45+
+
46+
If all authentication methods are allowed, then leave this empty.
47+
+
48+
For more options, see the OASIS standard link:https://docs.oasis-open.org/security/saml/v2.0/saml-authn-context-2.0-os.pdf[Authentication Context for SAML V2.0], Section 3.4: Schemas.
4549

4650
Before Azure and TigerGraph can successfully communicate, the Azure AD groups need to be correctly mapped to TigerGraph proxy groups with the appropriate roles.
4751
The TigerGraph proxy group is created with the `key=value` proxy rule. The key and value should match the SSO user claims in the SAML response.

0 commit comments

Comments
 (0)