Mirrors/unleash.unleash
1
0
Fork 0
mirror of https://github.com/Unleash/unleash.git synced 2025-09-10 17:53:36 +02:00
Code Issues Projects Releases Wiki Activity

docs: extend details on group limits and patch a crash bug

Browse Source
This commit is contained in:
sighphyre 2023-05-11 11:45:25 +02:00
parent 79f887bf89
commit 4640f2b37d
No known key found for this signature in database
GPG Key ID: 272209E090ED6733
1 changed files with 15 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
website/docs/how-to/how-to-add-sso-azure-saml.md
View File

@ -82,7 +82,7 @@ In order to configure SSO with SAML with your Unleash enterprise you should navi
![Unleash: sso-config screen](/img/sso-configure-saml.png) ![Unleash: sso-config screen](/img/sso-configure-saml.png)
Use the values from the [previous section](#azure-details) to fill out the form: Use the values from the [previous section](#azure-details) to fill out the form:
1. In the entity ID field, add the **Azure AD identifier**. It should look a little like this `https://sts.windows.net/<identifier>. 1. In the entity ID field, add the **Azure AD identifier**. It should look a little like this `https://sts.windows.net/<identifier>`.
2. In the single sign-on URL field, add the **login URL**. It should look something like `https://login.microsoftonline.com/<identifier>/saml2` 2. In the single sign-on URL field, add the **login URL**. It should look something like `https://login.microsoftonline.com/<identifier>/saml2`
3. In the X.509 certificate field, add the content of the `X509Certificate` tag from the **federation metadata XML**. 3. In the X.509 certificate field, add the content of the `X509Certificate` tag from the **federation metadata XML**.
@ -107,8 +107,11 @@ In section 2 (Attributes and claims) of the Azure SAML set-up, select the option
Check the box to "Customize the name of the group claim" and update the "Name" to something simple, such as "groups". Check the box to "Customize the name of the group claim" and update the "Name" to something simple, such as "groups".
Azure AD only supports sending a maximum of 150 groups in the SAML response. If you're using Azure AD and have users that are present in more than 150 groups, you'll need to add a filter in this section to the group claim to ensure that only the groups you want to sync are sent to Unleash.
![Azure: section 2, attributes and claims, adding a group claim with the name 'group'](/img/sso-azure-saml-group-setup.png) ![Azure: section 2, attributes and claims, adding a group claim with the name 'group'](/img/sso-azure-saml-group-setup.png)
**b) Unleash SSO Setup** **b) Unleash SSO Setup**
In the Unleash Admin SSO section, enable the option to "Enable Group Syncing". In the Unleash Admin SSO section, enable the option to "Enable Group Syncing".