Update brocade-sannav-management-portal-tutorial.md#1967
Update brocade-sannav-management-portal-tutorial.md#1967poonam-dilipgade-cpu wants to merge 28 commits into
Conversation
Updated groups and username mapping details
|
Learn Build status updates of commit 2272514: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Learn Build status updates of commit 760f392: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Learn Build status updates of commit e783584: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Learn Build status updates of commit 5fe8732: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Learn Build status updates of commit f7454a6:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md | Details |
docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md
- Line 90, Column 1: [Warning: code-block-indented - See documentation]
Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
|
Learn Build status updates of commit dc4c2a3:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md | Details |
docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md
- Line 90, Column 1: [Warning: code-block-indented - See documentation]
Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
|
Learn Build status updates of commit 53d843b:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md | Details |
docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md
- Line 96, Column 1: [Warning: code-block-indented - See documentation]
Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
|
Can you review the proposed changes? Note that the warnings will need to be resolved and the formatting for the added Note content fixed before the PR can be merged. Thanks. IMPORTANT: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
There was a problem hiding this comment.
Pull request overview
This PR updates the Brocade SANnav Management Portal SAML attribute guidance in the Microsoft Entra ID SaaS app tutorial to reflect updated group and username mapping details.
Changes:
- Updates the username claim mapping from
user.displaynametouser.userprincipalname. - Adds additional in-article guidance for configuring SANnav-specific groups and username attributes in Attributes & Claims.
| > [!Note] | ||
| > Please refer [this](~/identity/hybrid/connect/how-to-connect-fed-group-claims.md#add-group-claims-to-tokens-for-saml-applications-using-sso-configuration) link on how to add the groups attribute in the Attributes & Claims section. | ||
|
|
||
| > Guidelines for updaing SANNav specific attributes: |
| > [!Note] | ||
| > Please refer [this](~/identity/hybrid/connect/how-to-connect-fed-group-claims.md#add-group-claims-to-tokens-for-saml-applications-using-sso-configuration) link on how to add the groups attribute in the Attributes & Claims section. | ||
|
|
||
| > Guidelines for updaing SANNav specific attributes: |
| > Please refer [this](~/identity/hybrid/connect/how-to-connect-fed-group-claims.md#add-group-claims-to-tokens-for-saml-applications-using-sso-configuration) link on how to add the groups attribute in the Attributes & Claims section. | ||
|
|
||
| > Guidelines for updaing SANNav specific attributes: | ||
|
|
||
| > **groups**: To ensure the application receives the user's group information correctly, you need to modify the "Attributes & Claims" settings. You need to change the source attribute from default value "None" to the actual source of truth for your groups. The "Claim name" must be renamed to "groups" using the "Customize the name of the group claim" option. | ||
|
|
||
| > **username**: Refer to the SANnav Management Portal User Guide for the supported username format. | ||
|
|
||
|
|
|
Learn Build status updates of commit 8b583c1: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Learn Build status updates of commit 36d6644: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Learn Build status updates of commit 5b9cf88:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md | Details |
docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md
- Line 92, Column 1: [Warning: code-block-indented - See documentation]
Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
|
Learn Build status updates of commit c5f305d: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Learn Build status updates of commit b25e828: ✅ Validation status: passed
For more details, please refer to the build report. |
| @@ -5,6 +5,7 @@ ms.reviewer: jomondi | |||
| ms.topic: how-to | |||
| ms.date: 03/25/2025 | |||
|
|
||
| > [!Note] | ||
| > Guidelines for updating SANnav-specific attributes: | ||
| > - **groups**: While the default claim URI is `http://schemas.microsoft.com/ws/2008/06/identity/claims/groups` under **Attributes & Claims**, the application specifically requires the shortened name **groups**. To configure this, edit the existing group claim (the claim whose name appears as `http://schemas.microsoft.com/ws/2008/06/identity/claims/groups` in the edit UI) . After selecting your preferred **Source attribute** (such as **Group ID** or **sAMAccountName**), expand the **Advanced options** to select **Customize the name of the group claim**. Finally, enter **groups** into the **Name** field to ensure the application correctly identifies user permissions. |
|
Learn Build status updates of commit 3ab3859: ✅ Validation status: passed
For more details, please refer to the build report. |
| > [!Note] | ||
| > Please refer [this](~/identity/hybrid/connect/how-to-connect-fed-group-claims.md#add-group-claims-to-tokens-for-saml-applications-using-sso-configuration) link on how to add the groups attribute in the Attributes & Claims section. | ||
|
|
||
| 1. On the **Set-up single sign-on with SAML** page, in the **SAML Signing Certificate** section, find **Federation Metadata XML** and select **Download** to download the certificate and save it on your computer. |
|
Learn Build status updates of commit 33012bf: ✅ Validation status: passed
For more details, please refer to the build report. |
| 1. Browse to **Entra ID** > **Enterprise apps** > **Brocade SANnav Management Portal** > **Single sign-on**. | ||
| 1. On the **Select a single sign-on method** page, select **SAML**. | ||
| 1. On the **Set up single sign-on with SAML** page, select the pencil icon for **Basic SAML Configuration** to edit the settings. | ||
| 1. On the **Set up Single Sign-On with SAML** page, select the pencil icon for **Basic SAML Configuration** to edit the settings. |
| > [!Note] | ||
| > Please refer [this](~/identity/hybrid/connect/how-to-connect-fed-group-claims.md#add-group-claims-to-tokens-for-saml-applications-using-sso-configuration) link on how to add the groups attribute in the Attributes & Claims section. | ||
|
|
||
| 1. On the **Set-up single sign-on with SAML** page, in the **SAML Signing Certificate** section, find **Federation Metadata XML** and select **Download** to download the certificate and save it on your computer. |
|
Learn Build status updates of commit f8d395e: ✅ Validation status: passed
For more details, please refer to the build report. |
|
refreshing the CLA |
|
@poonam-dilipgade-cpu please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
|
|
@poonam-dilipgade-cpu Thank you for your contribution. Would you take a moment to sign the Contributor License Agreement (CLA)? After the CLA is signed, someone can review your pull request. Thanks! #label:"aq-pr-triaged" |
|
Learn Build status updates of commit f8d395e: ✅ Validation status: passed
For more details, please refer to the build report. |
@v-dirichards |
@poonam-dilipgade-cpu Yes, it is mandatory to sign the CLA. We cannot merge the PR without it. |
|
@poonam-dilipgade-cpu please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
|
|
Learn Build status updates of commit dab80dc: ✅ Validation status: passed
For more details, please refer to the build report. |
|
@poonam-dilipgade-cpu please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
|
|
Learn Build status updates of commit c04e991: ✅ Validation status: passed
For more details, please refer to the build report. |
Description:
This PR updates the Brocade SANnav Management Portal tutorial to provide specific requirements for attribute mapping and group authorization.
Summary of Changes
Group Claims Configuration: Added explicit instructions to include a groups attribute in the Attributes & Claims section. This includes changing the source attribute from None to a valid group source and customizing the claim name to exactly groups for application compatibility.
Username Alignment: Added a requirement for administrators to align the Entra ID username claim with the specific formats supported in the SANnav Management Portal User Guide.