From 2272514804cfc44ae6ee4a6d5398129630a269aa Mon Sep 17 00:00:00 2001 From: poonam-dilipgade-cpu Date: Mon, 11 May 2026 14:47:00 +0530 Subject: [PATCH 01/26] Update brocade-sannav-management-portal-tutorial.md Updated groups and username mapping details --- .../saas-apps/brocade-sannav-management-portal-tutorial.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md b/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md index 6e6c576ba5f..5f68af4135e 100644 --- a/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md +++ b/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md @@ -82,6 +82,8 @@ Follow these steps to enable Microsoft Entra SSO in the Microsoft Entra admin ce ![Screenshot shows user attributes and claims with default values.](common/default-attributes.png "Claims") 1. In addition, Brocade SANnav Management Portal application expects a few more attributes to be passed back in SAML response which are shown below. These attributes are also pre populated but you can review them as per your requirements. + **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" using option. + **username**: Refer to the SANnav user guide for the supported username format. | Name | Source Attribute| | ---------------| --------- | From 760f3926c0b30dc26b71b42a7e6699d61c8f91e9 Mon Sep 17 00:00:00 2001 From: poonam-dilipgade-cpu Date: Mon, 11 May 2026 15:01:16 +0530 Subject: [PATCH 02/26] Update brocade-sannav-management-portal-tutorial.md --- .../saas-apps/brocade-sannav-management-portal-tutorial.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md b/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md index 5f68af4135e..8066f5ccda6 100644 --- a/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md +++ b/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md @@ -82,7 +82,9 @@ Follow these steps to enable Microsoft Entra SSO in the Microsoft Entra admin ce ![Screenshot shows user attributes and claims with default values.](common/default-attributes.png "Claims") 1. In addition, Brocade SANnav Management Portal application expects a few more attributes to be passed back in SAML response which are shown below. These attributes are also pre populated but you can review them as per your requirements. + **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" using option. + **username**: Refer to the SANnav user guide for the supported username format. | Name | Source Attribute| From e783584cd1c4e976238d60c57bf9e0a7917512f0 Mon Sep 17 00:00:00 2001 From: poonam-dilipgade-cpu Date: Mon, 11 May 2026 15:43:48 +0530 Subject: [PATCH 03/26] Update brocade-sannav-management-portal-tutorial.md --- .../saas-apps/brocade-sannav-management-portal-tutorial.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md b/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md index 8066f5ccda6..9e922113b65 100644 --- a/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md +++ b/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md @@ -90,7 +90,7 @@ Follow these steps to enable Microsoft Entra SSO in the Microsoft Entra admin ce | Name | Source Attribute| | ---------------| --------- | | groups | user.groups | - | username | user.displayname | + | username | user.userprincipalname | > [!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. From 5fe873240fafbd698bde5a5344edf63e7350eea3 Mon Sep 17 00:00:00 2001 From: poonam-dilipgade-cpu Date: Mon, 11 May 2026 19:38:17 +0530 Subject: [PATCH 04/26] Update brocade-sannav-management-portal-tutorial.md --- .../saas-apps/brocade-sannav-management-portal-tutorial.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md b/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md index 9e922113b65..e7f6ebad687 100644 --- a/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md +++ b/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md @@ -83,9 +83,9 @@ Follow these steps to enable Microsoft Entra SSO in the Microsoft Entra admin ce 1. In addition, Brocade SANnav Management Portal application expects a few more attributes to be passed back in SAML response which are shown below. These attributes are also pre populated but you can review them as per your requirements. - **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" using option. + **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 user guide for the supported username format. + **username**: Refer to the SANnav Management Portal User Guide for the supported username format. | Name | Source Attribute| | ---------------| --------- | From f7454a6190084e6d1f85cf8c557565849fcff895 Mon Sep 17 00:00:00 2001 From: poonam-dilipgade-cpu Date: Mon, 11 May 2026 19:39:21 +0530 Subject: [PATCH 05/26] Update brocade-sannav-management-portal-tutorial.md --- .../saas-apps/brocade-sannav-management-portal-tutorial.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md b/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md index e7f6ebad687..b6c08258226 100644 --- a/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md +++ b/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md @@ -83,9 +83,9 @@ Follow these steps to enable Microsoft Entra SSO in the Microsoft Entra admin ce 1. In addition, Brocade SANnav Management Portal application expects a few more attributes to be passed back in SAML response which are shown below. These attributes are also pre populated but you can review them as per your requirements. - **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. +**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. +**username**: Refer to the SANnav Management Portal User Guide for the supported username format. | Name | Source Attribute| | ---------------| --------- | From dc4c2a362f6a01ec7d6213a4f2d77e46909c7fd1 Mon Sep 17 00:00:00 2001 From: poonam-dilipgade-cpu Date: Mon, 11 May 2026 19:50:01 +0530 Subject: [PATCH 06/26] Update brocade-sannav-management-portal-tutorial.md --- .../saas-apps/brocade-sannav-management-portal-tutorial.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md b/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md index b6c08258226..8269cbbc917 100644 --- a/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md +++ b/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md @@ -83,7 +83,7 @@ Follow these steps to enable Microsoft Entra SSO in the Microsoft Entra admin ce 1. In addition, Brocade SANnav Management Portal application expects a few more attributes to be passed back in SAML response which are shown below. These attributes are also pre populated but you can review them as per your requirements. -**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. +**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. From 53d843bcd664674720dfc8f333ce6e85dd991922 Mon Sep 17 00:00:00 2001 From: poonam-dilipgade-cpu Date: Mon, 11 May 2026 20:00:51 +0530 Subject: [PATCH 07/26] Update brocade-sannav-management-portal-tutorial.md --- .../brocade-sannav-management-portal-tutorial.md | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md b/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md index 8269cbbc917..3b31c2d0e87 100644 --- a/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md +++ b/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md @@ -82,10 +82,6 @@ Follow these steps to enable Microsoft Entra SSO in the Microsoft Entra admin ce ![Screenshot shows user attributes and claims with default values.](common/default-attributes.png "Claims") 1. In addition, Brocade SANnav Management Portal application expects a few more attributes to be passed back in SAML response which are shown below. These attributes are also pre populated but you can review them as per your requirements. - -**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. | Name | Source Attribute| | ---------------| --------- | @@ -94,6 +90,13 @@ Follow these steps to enable Microsoft Entra SSO in the Microsoft Entra admin ce > [!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: + + > **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. + 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. From 8b583c1144838b4eab487e457a2a5498bbddb7a8 Mon Sep 17 00:00:00 2001 From: poonam-dilipgade-cpu Date: Mon, 11 May 2026 20:54:24 +0530 Subject: [PATCH 08/26] Update brocade-sannav-management-portal-tutorial.md --- .../saas-apps/brocade-sannav-management-portal-tutorial.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md b/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md index 3b31c2d0e87..7d24a9baa39 100644 --- a/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md +++ b/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md @@ -93,9 +93,9 @@ Follow these steps to enable Microsoft Entra SSO in the Microsoft Entra admin ce > 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. + > **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. 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. From 36d6644ee87387a52bec5408e0b9dd275acf9c98 Mon Sep 17 00:00:00 2001 From: poonam-dilipgade-cpu Date: Mon, 11 May 2026 20:57:58 +0530 Subject: [PATCH 09/26] corrected typo --- .../saas-apps/brocade-sannav-management-portal-tutorial.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md b/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md index 7d24a9baa39..b611d0f31a7 100644 --- a/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md +++ b/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md @@ -91,7 +91,7 @@ Follow these steps to enable Microsoft Entra SSO in the Microsoft Entra admin ce > [!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: + > Guidelines for updating 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. From 5b9cf8837b4f1b14c863ac500dce363fa3c3b69a Mon Sep 17 00:00:00 2001 From: poonam-dilipgade-cpu Date: Mon, 11 May 2026 21:03:11 +0530 Subject: [PATCH 10/26] Addressed review comments --- .../brocade-sannav-management-portal-tutorial.md | 12 +++++------- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md b/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md index b611d0f31a7..9a460faa4a5 100644 --- a/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md +++ b/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md @@ -89,13 +89,11 @@ Follow these steps to enable Microsoft Entra SSO in the Microsoft Entra admin ce | username | user.userprincipalname | > [!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 updating 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. + > Refer to [Add group claims to tokens for SAML applications using SSO configuration](~/identity/hybrid/connect/how-to-connect-fed-group-claims.md#add-group-claims-to-tokens-for-saml-applications-using-sso-configuration) to add the `groups` attribute in the **Attributes & Claims** section. + > + > Guidelines for updating SANnav-specific attributes: + > - **groups**: To ensure the application receives the user's group information correctly, modify the **Attributes & Claims** settings. Change the source attribute from the default value of `None` to the actual source of truth for your groups. Rename **Claim name** to `groups` by using the **Customize the name of the group claim** option. + > - **username**: Refer to the SANnav Management Portal User Guide for the supported username format. 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. From c5f305d3abeb8b82bf40f94dd9491ee8083e8009 Mon Sep 17 00:00:00 2001 From: poonam-dilipgade-cpu Date: Mon, 11 May 2026 22:23:44 +0530 Subject: [PATCH 11/26] Fixed indentation --- .../saas-apps/brocade-sannav-management-portal-tutorial.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md b/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md index 9a460faa4a5..2d2dd8cd9a8 100644 --- a/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md +++ b/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md @@ -89,7 +89,7 @@ Follow these steps to enable Microsoft Entra SSO in the Microsoft Entra admin ce | username | user.userprincipalname | > [!Note] - > Refer to [Add group claims to tokens for SAML applications using SSO configuration](~/identity/hybrid/connect/how-to-connect-fed-group-claims.md#add-group-claims-to-tokens-for-saml-applications-using-sso-configuration) to add the `groups` attribute in the **Attributes & Claims** section. + > Refer to [Add group claims to tokens for SAML applications using SSO configuration](~/identity/hybrid/connect/how-to-connect-fed-group-claims.md#add-group-claims-to-tokens-for-saml-applications-using-sso-configuration) to add the `groups` attribute in the **Attributes & Claims** section. > > Guidelines for updating SANnav-specific attributes: > - **groups**: To ensure the application receives the user's group information correctly, modify the **Attributes & Claims** settings. Change the source attribute from the default value of `None` to the actual source of truth for your groups. Rename **Claim name** to `groups` by using the **Customize the name of the group claim** option. From 322e01587dcc461565e0c82fb4460821303750b7 Mon Sep 17 00:00:00 2001 From: poonam-dilipgade-cpu Date: Mon, 11 May 2026 22:26:16 +0530 Subject: [PATCH 12/26] Fixed indentation --- .../saas-apps/brocade-sannav-management-portal-tutorial.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md b/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md index 2d2dd8cd9a8..ddbe2b847b2 100644 --- a/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md +++ b/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md @@ -89,6 +89,7 @@ Follow these steps to enable Microsoft Entra SSO in the Microsoft Entra admin ce | username | user.userprincipalname | > [!Note] + > > Refer to [Add group claims to tokens for SAML applications using SSO configuration](~/identity/hybrid/connect/how-to-connect-fed-group-claims.md#add-group-claims-to-tokens-for-saml-applications-using-sso-configuration) to add the `groups` attribute in the **Attributes & Claims** section. > > Guidelines for updating SANnav-specific attributes: From 27125a6e4432861f5b8a4241483de031eb5d0845 Mon Sep 17 00:00:00 2001 From: poonam-dilipgade-cpu Date: Tue, 12 May 2026 11:55:09 +0530 Subject: [PATCH 13/26] Addressed review comment --- .../brocade-sannav-management-portal-tutorial.md | 13 +++++-------- 1 file changed, 5 insertions(+), 8 deletions(-) diff --git a/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md b/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md index ddbe2b847b2..4e783c917be 100644 --- a/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md +++ b/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md @@ -88,14 +88,11 @@ Follow these steps to enable Microsoft Entra SSO in the Microsoft Entra admin ce | groups | user.groups | | username | user.userprincipalname | - > [!Note] - > - > Refer to [Add group claims to tokens for SAML applications using SSO configuration](~/identity/hybrid/connect/how-to-connect-fed-group-claims.md#add-group-claims-to-tokens-for-saml-applications-using-sso-configuration) to add the `groups` attribute in the **Attributes & Claims** section. - > - > Guidelines for updating SANnav-specific attributes: - > - **groups**: To ensure the application receives the user's group information correctly, modify the **Attributes & Claims** settings. Change the source attribute from the default value of `None` to the actual source of truth for your groups. Rename **Claim name** to `groups` by using the **Customize the name of the group claim** option. - > - **username**: Refer to the SANnav Management Portal User Guide for the supported username format. - +> [!Note] +> Refer to [Add group claims to tokens for SAML applications using SSO configuration](~/identity/hybrid/connect/how-to-connect-fed-group-claims.md#add-group-claims-to-tokens-for-saml-applications-using-sso-configuration) to add the `groups` attribute in the **Attributes & Claims** section. +> Guidelines for updating SANnav-specific attributes: +> - **groups**: To ensure the application receives the user's group information correctly, modify the **Attributes & Claims** settings. Change the source attribute from the default value of `None` to the actual source of truth for your groups. Rename **Claim name** to `groups` by using the **Customize the name of the group claim** option. +> - **username**: Refer to the SANnav Management Portal User Guide for the supported username format. 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. From 36d0ccc54fc9615512a7e15a37fc6b8a1b3e9481 Mon Sep 17 00:00:00 2001 From: poonam-dilipgade-cpu Date: Tue, 12 May 2026 12:11:23 +0530 Subject: [PATCH 14/26] Fixed indentation --- .../saas-apps/brocade-sannav-management-portal-tutorial.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md b/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md index 4e783c917be..dffcb76cb1d 100644 --- a/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md +++ b/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md @@ -94,6 +94,12 @@ Follow these steps to enable Microsoft Entra SSO in the Microsoft Entra admin ce > - **groups**: To ensure the application receives the user's group information correctly, modify the **Attributes & Claims** settings. Change the source attribute from the default value of `None` to the actual source of truth for your groups. Rename **Claim name** to `groups` by using the **Customize the name of the group claim** option. > - **username**: Refer to the SANnav Management Portal User Guide for the supported username format. + > [!Note] + > Refer to [Add group claims to tokens for SAML applications using SSO configuration](~/identity/hybrid/connect/how-to-connect-fed-group-claims.md#add-group-claims-to-tokens-for-saml-applications-using-sso-configuration) to add the `groups` attribute in the **Attributes & Claims** section. + > Guidelines for updating SANnav-specific attributes: + > - **groups**: To ensure the application receives the user's group information correctly, **Add a group claim** in the **Attributes & Claims** settings. Pick the appropriate **Source attribute** from the drop-down (for example, ObjectId or synced attributes). Then, select the **Customize the name of the group claim** option and enter `groups` in the **Name** field. + > - **username**: Refer to the SANnav Management Portal User Guide for the supported username format. + 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. ![Screenshot shows the Certificate download link.](common/metadataxml.png "Certificate") From d69193c55d3c23460e00aab30a5bd3f23c9af444 Mon Sep 17 00:00:00 2001 From: poonam-dilipgade-cpu Date: Tue, 12 May 2026 12:13:23 +0530 Subject: [PATCH 15/26] Fixed indentation --- .../saas-apps/brocade-sannav-management-portal-tutorial.md | 6 ------ 1 file changed, 6 deletions(-) diff --git a/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md b/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md index dffcb76cb1d..c3f81d4ed75 100644 --- a/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md +++ b/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md @@ -88,12 +88,6 @@ Follow these steps to enable Microsoft Entra SSO in the Microsoft Entra admin ce | groups | user.groups | | username | user.userprincipalname | -> [!Note] -> Refer to [Add group claims to tokens for SAML applications using SSO configuration](~/identity/hybrid/connect/how-to-connect-fed-group-claims.md#add-group-claims-to-tokens-for-saml-applications-using-sso-configuration) to add the `groups` attribute in the **Attributes & Claims** section. -> Guidelines for updating SANnav-specific attributes: -> - **groups**: To ensure the application receives the user's group information correctly, modify the **Attributes & Claims** settings. Change the source attribute from the default value of `None` to the actual source of truth for your groups. Rename **Claim name** to `groups` by using the **Customize the name of the group claim** option. -> - **username**: Refer to the SANnav Management Portal User Guide for the supported username format. - > [!Note] > Refer to [Add group claims to tokens for SAML applications using SSO configuration](~/identity/hybrid/connect/how-to-connect-fed-group-claims.md#add-group-claims-to-tokens-for-saml-applications-using-sso-configuration) to add the `groups` attribute in the **Attributes & Claims** section. > Guidelines for updating SANnav-specific attributes: From 23e78820e45aa61746eb49696004a66be9d62b32 Mon Sep 17 00:00:00 2001 From: poonam-dilipgade-cpu Date: Tue, 12 May 2026 12:30:54 +0530 Subject: [PATCH 16/26] Updated the content --- .../saas-apps/brocade-sannav-management-portal-tutorial.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md b/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md index c3f81d4ed75..e99e8ec63e1 100644 --- a/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md +++ b/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md @@ -91,7 +91,7 @@ Follow these steps to enable Microsoft Entra SSO in the Microsoft Entra admin ce > [!Note] > Refer to [Add group claims to tokens for SAML applications using SSO configuration](~/identity/hybrid/connect/how-to-connect-fed-group-claims.md#add-group-claims-to-tokens-for-saml-applications-using-sso-configuration) to add the `groups` attribute in the **Attributes & Claims** section. > Guidelines for updating SANnav-specific attributes: - > - **groups**: To ensure the application receives the user's group information correctly, **Add a group claim** in the **Attributes & Claims** settings. Pick the appropriate **Source attribute** from the drop-down (for example, ObjectId or synced attributes). Then, select the **Customize the name of the group claim** option and enter `groups` in the **Name** field. + > - **groups**: To ensure the application receives the user's group information correctly, update the existing groups claim in the **Attributes & Claims** settings. Pick the appropriate **Source attribute** from the drop-down list (for example, **Group ID** or **sAMAccountName**). Then, select the **Customize the name of the group claim** option and enter `groups` in the **Name** field. > - **username**: Refer to the SANnav Management Portal User Guide for the supported username format. 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. From a836d078c92b366baf75a70bbfbf5552a9c92485 Mon Sep 17 00:00:00 2001 From: poonam-dilipgade-cpu Date: Tue, 12 May 2026 12:49:52 +0530 Subject: [PATCH 17/26] Updated the content --- .../saas-apps/brocade-sannav-management-portal-tutorial.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md b/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md index e99e8ec63e1..3ca2bed9ac2 100644 --- a/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md +++ b/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md @@ -89,11 +89,12 @@ Follow these steps to enable Microsoft Entra SSO in the Microsoft Entra admin ce | username | user.userprincipalname | > [!Note] - > Refer to [Add group claims to tokens for SAML applications using SSO configuration](~/identity/hybrid/connect/how-to-connect-fed-group-claims.md#add-group-claims-to-tokens-for-saml-applications-using-sso-configuration) to add the `groups` attribute in the **Attributes & Claims** section. > Guidelines for updating SANnav-specific attributes: - > - **groups**: To ensure the application receives the user's group information correctly, update the existing groups claim in the **Attributes & Claims** settings. Pick the appropriate **Source attribute** from the drop-down list (for example, **Group ID** or **sAMAccountName**). Then, select the **Customize the name of the group claim** option and enter `groups` in the **Name** field. + > - **groups**: To ensure the application receives the user's group information correctly, update the existing groups claim with Claim name **http://schemas.microsoft.com/ws/2008/06/identity/claims/groups** in the **Attributes & Claims** settings. Pick the appropriate **Source attribute** from the drop-down list (for example, **Group ID** or **sAMAccountName**). Then, select the **Customize the name of the group claim** option under **Advanced options** and enter `groups` in the **Name** field. + > Refer to [Add group claims to tokens for SAML applications using SSO configuration](~/identity/hybrid/connect/how-to-connect-fed-group-claims.md#add-group-claims-to-tokens-for-saml-applications-using-sso-configuration) to know more about the `groups` attribute in the **Attributes & Claims** section. > - **username**: Refer to the SANnav Management Portal User Guide for the supported username format. + 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. ![Screenshot shows the Certificate download link.](common/metadataxml.png "Certificate") From f3d6001d9de1a5f7d69f1c432a98882f82bdcd26 Mon Sep 17 00:00:00 2001 From: poonam-dilipgade-cpu Date: Tue, 12 May 2026 13:16:56 +0530 Subject: [PATCH 18/26] Update brocade-sannav-management-portal-tutorial.md --- .../saas-apps/brocade-sannav-management-portal-tutorial.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md b/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md index 3ca2bed9ac2..beff953187f 100644 --- a/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md +++ b/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md @@ -90,7 +90,7 @@ Follow these steps to enable Microsoft Entra SSO in the Microsoft Entra admin ce > [!Note] > Guidelines for updating SANnav-specific attributes: - > - **groups**: To ensure the application receives the user's group information correctly, update the existing groups claim with Claim name **http://schemas.microsoft.com/ws/2008/06/identity/claims/groups** in the **Attributes & Claims** settings. Pick the appropriate **Source attribute** from the drop-down list (for example, **Group ID** or **sAMAccountName**). Then, select the **Customize the name of the group claim** option under **Advanced options** and enter `groups` in the **Name** field. + > - **groups**: To ensure the application receives the user's group information correctly, update the existing groups claim with Claim name `http://schemas.microsoft.com/ws/2008/06/identity/claims/groups` in the **Attributes & Claims** settings. Pick the appropriate **Source attribute** from the drop-down list (for example, **Group ID** or **sAMAccountName**). Then, select the **Customize the name of the group claim** option under **Advanced options** and enter `groups` in the **Name** field. > Refer to [Add group claims to tokens for SAML applications using SSO configuration](~/identity/hybrid/connect/how-to-connect-fed-group-claims.md#add-group-claims-to-tokens-for-saml-applications-using-sso-configuration) to know more about the `groups` attribute in the **Attributes & Claims** section. > - **username**: Refer to the SANnav Management Portal User Guide for the supported username format. From 8291ae92baf726dcc626f3da67746e09241cffdd Mon Sep 17 00:00:00 2001 From: poonam-dilipgade-cpu Date: Tue, 12 May 2026 14:27:04 +0530 Subject: [PATCH 19/26] updated --- .../saas-apps/brocade-sannav-management-portal-tutorial.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md b/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md index beff953187f..10f09d0a04c 100644 --- a/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md +++ b/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md @@ -91,8 +91,8 @@ Follow these steps to enable Microsoft Entra SSO in the Microsoft Entra admin ce > [!Note] > Guidelines for updating SANnav-specific attributes: > - **groups**: To ensure the application receives the user's group information correctly, update the existing groups claim with Claim name `http://schemas.microsoft.com/ws/2008/06/identity/claims/groups` in the **Attributes & Claims** settings. Pick the appropriate **Source attribute** from the drop-down list (for example, **Group ID** or **sAMAccountName**). Then, select the **Customize the name of the group claim** option under **Advanced options** and enter `groups` in the **Name** field. - > Refer to [Add group claims to tokens for SAML applications using SSO configuration](~/identity/hybrid/connect/how-to-connect-fed-group-claims.md#add-group-claims-to-tokens-for-saml-applications-using-sso-configuration) to know more about the `groups` attribute in the **Attributes & Claims** section. - > - **username**: Refer to the SANnav Management Portal User Guide for the supported username format. + > Refer to [Add group claims to tokens for SAML applications using SSO configuration](~/identity/hybrid/connect/how-to-connect-fed-group-claims.md#add-group-claims-to-tokens-for-saml-applications-using-sso-configuration) to learn more about the `groups` attribute in the **Attributes & Claims** section. + > - **username**: We recommend using the User Principal Name (UPN) format for SANnav usernames. While you can modify the username claim to suit your specific requirements, please ensure the format complies with the standards outlined in the SANnav Management Portal User Guide. 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. From a0237f71fdab2b37be3b07d2f9cd347ab45e328e Mon Sep 17 00:00:00 2001 From: poonam-dilipgade-cpu Date: Tue, 12 May 2026 14:37:45 +0530 Subject: [PATCH 20/26] Update brocade-sannav-management-portal-tutorial.md --- .../brocade-sannav-management-portal-tutorial.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md b/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md index 10f09d0a04c..19f0bc7adb7 100644 --- a/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md +++ b/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md @@ -83,16 +83,16 @@ Follow these steps to enable Microsoft Entra SSO in the Microsoft Entra admin ce 1. In addition, Brocade SANnav Management Portal application expects a few more attributes to be passed back in SAML response which are shown below. These attributes are also pre populated but you can review them as per your requirements. - | Name | Source Attribute| - | ---------------| --------- | - | groups | user.groups | - | username | user.userprincipalname | + | Name | Source Attribute| + | ---------------| --------- | + | groups | user.groups | + | username | user.userprincipalname | > [!Note] > Guidelines for updating SANnav-specific attributes: - > - **groups**: To ensure the application receives the user's group information correctly, update the existing groups claim with Claim name `http://schemas.microsoft.com/ws/2008/06/identity/claims/groups` in the **Attributes & Claims** settings. Pick the appropriate **Source attribute** from the drop-down list (for example, **Group ID** or **sAMAccountName**). Then, select the **Customize the name of the group claim** option under **Advanced options** and enter `groups` in the **Name** field. + > - **groups**: The claim might appear as the URL `http://schemas.microsoft.com/ws/2008/06/identity/claims/groups` by default in the edit experience, but the expected final claim name for the app is **groups**. To ensure the application receives the user's group information correctly, update the existing groups claim with Claim name `http://schemas.microsoft.com/ws/2008/06/identity/claims/groups` in the **Attributes & Claims** settings. Pick the appropriate **Source attribute** from the drop-down list (for example, **Group ID** or **sAMAccountName**). Then, select the **Customize the name of the group claim** option under **Advanced options** and enter `groups` in the **Name** field. > Refer to [Add group claims to tokens for SAML applications using SSO configuration](~/identity/hybrid/connect/how-to-connect-fed-group-claims.md#add-group-claims-to-tokens-for-saml-applications-using-sso-configuration) to learn more about the `groups` attribute in the **Attributes & Claims** section. - > - **username**: We recommend using the User Principal Name (UPN) format for SANnav usernames. While you can modify the username claim to suit your specific requirements, please ensure the format complies with the standards outlined in the SANnav Management Portal User Guide. + > - **username**: We recommend using the User Principal Name (UPN) format for SANnav usernames. While you can modify the username claim to suit your specific requirements, make sure the format complies with the standards outlined in the SANnav Management Portal User Guide. 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. From f44abe0654d5df758946fadc51973fd7e6a5996c Mon Sep 17 00:00:00 2001 From: poonam-dilipgade-cpu Date: Tue, 12 May 2026 14:52:18 +0530 Subject: [PATCH 21/26] Update brocade-sannav-management-portal-tutorial.md --- .../saas-apps/brocade-sannav-management-portal-tutorial.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md b/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md index 19f0bc7adb7..5227ef224f3 100644 --- a/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md +++ b/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md @@ -5,6 +5,7 @@ ms.reviewer: jomondi ms.topic: how-to ms.date: 03/25/2025 ms.custom: sfi-image-nochange +ai-usage: ai-assisted # Customer intent: As an IT administrator, I want to learn how to configure single sign-on between Microsoft Entra ID and Brocade SANnav Management Portal so that I can control who has access to Brocade SANnav Management Portal, enable automatic sign-in with Microsoft Entra accounts, and manage my accounts in one central location. --- @@ -81,7 +82,7 @@ Follow these steps to enable Microsoft Entra SSO in the Microsoft Entra admin ce ![Screenshot shows user attributes and claims with default values.](common/default-attributes.png "Claims") -1. In addition, Brocade SANnav Management Portal application expects a few more attributes to be passed back in SAML response which are shown below. These attributes are also pre populated but you can review them as per your requirements. +1. In addition, Brocade SANnav Management Portal application expects a few more attributes to be passed back in SAML response which are shown below. These attributes are also prepopulated but you can review them as per your requirements. | Name | Source Attribute| | ---------------| --------- | @@ -90,9 +91,9 @@ Follow these steps to enable Microsoft Entra SSO in the Microsoft Entra admin ce > [!Note] > Guidelines for updating SANnav-specific attributes: - > - **groups**: The claim might appear as the URL `http://schemas.microsoft.com/ws/2008/06/identity/claims/groups` by default in the edit experience, but the expected final claim name for the app is **groups**. To ensure the application receives the user's group information correctly, update the existing groups claim with Claim name `http://schemas.microsoft.com/ws/2008/06/identity/claims/groups` in the **Attributes & Claims** settings. Pick the appropriate **Source attribute** from the drop-down list (for example, **Group ID** or **sAMAccountName**). Then, select the **Customize the name of the group claim** option under **Advanced options** and enter `groups` in the **Name** field. + > - **groups**: The claim might appear as the URL `http://schemas.microsoft.com/ws/2008/06/identity/claims/groups` by default in the edit experience, but the expected final claim name for the application is **groups**. To ensure the application receives the user's group information correctly, update the existing groups claim with Claim name `http://schemas.microsoft.com/ws/2008/06/identity/claims/groups` in the **Attributes & Claims** settings. Pick the appropriate **Source attribute** from the drop-down list (for example, **Group ID** or **sAMAccountName**). Then, select the **Customize the name of the group claim** option under **Advanced options** and enter `groups` in the **Name** field. > Refer to [Add group claims to tokens for SAML applications using SSO configuration](~/identity/hybrid/connect/how-to-connect-fed-group-claims.md#add-group-claims-to-tokens-for-saml-applications-using-sso-configuration) to learn more about the `groups` attribute in the **Attributes & Claims** section. - > - **username**: We recommend using the User Principal Name (UPN) format for SANnav usernames. While you can modify the username claim to suit your specific requirements, make sure the format complies with the standards outlined in the SANnav Management Portal User Guide. + > - **username**: Use the User Principal Name (UPN) format for SANnav usernames. While you can modify the username claim to suit your specific requirements, make sure the format complies with the standards outlined in the SANnav Management Portal User Guide. 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. From 2521963b974d53d26c8dcaeea3e13aa6a4856ce0 Mon Sep 17 00:00:00 2001 From: poonam-dilipgade-cpu Date: Tue, 12 May 2026 15:12:49 +0530 Subject: [PATCH 22/26] Update brocade-sannav-management-portal-tutorial.md --- .../saas-apps/brocade-sannav-management-portal-tutorial.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md b/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md index 5227ef224f3..b1bbdca03ba 100644 --- a/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md +++ b/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md @@ -82,7 +82,7 @@ Follow these steps to enable Microsoft Entra SSO in the Microsoft Entra admin ce ![Screenshot shows user attributes and claims with default values.](common/default-attributes.png "Claims") -1. In addition, Brocade SANnav Management Portal application expects a few more attributes to be passed back in SAML response which are shown below. These attributes are also prepopulated but you can review them as per your requirements. +1. The Brocade SANnav Management Portal requires several additional attributes within the SAML response. While these attributes are pre-configured by default, they should be reviewed to ensure they align with your specific environment and security requirements. The following table outlines the expected attributes: | Name | Source Attribute| | ---------------| --------- | @@ -91,7 +91,7 @@ Follow these steps to enable Microsoft Entra SSO in the Microsoft Entra admin ce > [!Note] > Guidelines for updating SANnav-specific attributes: - > - **groups**: The claim might appear as the URL `http://schemas.microsoft.com/ws/2008/06/identity/claims/groups` by default in the edit experience, but the expected final claim name for the application is **groups**. To ensure the application receives the user's group information correctly, update the existing groups claim with Claim name `http://schemas.microsoft.com/ws/2008/06/identity/claims/groups` in the **Attributes & Claims** settings. Pick the appropriate **Source attribute** from the drop-down list (for example, **Group ID** or **sAMAccountName**). Then, select the **Customize the name of the group claim** option under **Advanced options** and enter `groups` in the **Name** field. + > - **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 with claim name `http://schemas.microsoft.com/ws/2008/06/identity/claims/groups`. 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. > Refer to [Add group claims to tokens for SAML applications using SSO configuration](~/identity/hybrid/connect/how-to-connect-fed-group-claims.md#add-group-claims-to-tokens-for-saml-applications-using-sso-configuration) to learn more about the `groups` attribute in the **Attributes & Claims** section. > - **username**: Use the User Principal Name (UPN) format for SANnav usernames. While you can modify the username claim to suit your specific requirements, make sure the format complies with the standards outlined in the SANnav Management Portal User Guide. From b25e8281cd0c92171dc7911458a068294479290f Mon Sep 17 00:00:00 2001 From: poonam-dilipgade-cpu Date: Tue, 12 May 2026 15:34:51 +0530 Subject: [PATCH 23/26] Update brocade-sannav-management-portal-tutorial.md --- .../saas-apps/brocade-sannav-management-portal-tutorial.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md b/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md index b1bbdca03ba..70524cfc92e 100644 --- a/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md +++ b/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md @@ -91,7 +91,7 @@ Follow these steps to enable Microsoft Entra SSO in the Microsoft Entra admin ce > [!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 with claim name `http://schemas.microsoft.com/ws/2008/06/identity/claims/groups`. 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. + > - **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. > Refer to [Add group claims to tokens for SAML applications using SSO configuration](~/identity/hybrid/connect/how-to-connect-fed-group-claims.md#add-group-claims-to-tokens-for-saml-applications-using-sso-configuration) to learn more about the `groups` attribute in the **Attributes & Claims** section. > - **username**: Use the User Principal Name (UPN) format for SANnav usernames. While you can modify the username claim to suit your specific requirements, make sure the format complies with the standards outlined in the SANnav Management Portal User Guide. From 3ab38597b3244c30c73fcef84493acabb988e5d5 Mon Sep 17 00:00:00 2001 From: poonam-dilipgade-cpu Date: Tue, 12 May 2026 15:45:17 +0530 Subject: [PATCH 24/26] Update brocade-sannav-management-portal-tutorial.md --- .../saas-apps/brocade-sannav-management-portal-tutorial.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md b/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md index 70524cfc92e..0c742954cb9 100644 --- a/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md +++ b/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md @@ -91,7 +91,7 @@ Follow these steps to enable Microsoft Entra SSO in the Microsoft Entra admin ce > [!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. + > - **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. > Refer to [Add group claims to tokens for SAML applications using SSO configuration](~/identity/hybrid/connect/how-to-connect-fed-group-claims.md#add-group-claims-to-tokens-for-saml-applications-using-sso-configuration) to learn more about the `groups` attribute in the **Attributes & Claims** section. > - **username**: Use the User Principal Name (UPN) format for SANnav usernames. While you can modify the username claim to suit your specific requirements, make sure the format complies with the standards outlined in the SANnav Management Portal User Guide. From 33012bf0bfb678a02bad61f150c87a728426e9c9 Mon Sep 17 00:00:00 2001 From: poonam-dilipgade-cpu Date: Tue, 12 May 2026 16:03:53 +0530 Subject: [PATCH 25/26] Update brocade-sannav-management-portal-tutorial.md --- .../saas-apps/brocade-sannav-management-portal-tutorial.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md b/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md index 0c742954cb9..24084270a6a 100644 --- a/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md +++ b/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md @@ -61,7 +61,7 @@ Follow these steps to enable Microsoft Entra SSO in the Microsoft Entra admin ce 1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Cloud Application Administrator](~/identity/role-based-access-control/permissions-reference.md#cloud-application-administrator). 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. ![Screenshot shows how to edit Basic SAML Configuration.](common/edit-urls.png "Basic Configuration") From f8d395ebd431e69205d1c3e17415a14f10f5f65c Mon Sep 17 00:00:00 2001 From: poonam-dilipgade-cpu Date: Tue, 12 May 2026 16:15:09 +0530 Subject: [PATCH 26/26] Update brocade-sannav-management-portal-tutorial.md --- .../saas-apps/brocade-sannav-management-portal-tutorial.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md b/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md index 24084270a6a..204ff2b170c 100644 --- a/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md +++ b/docs/identity/saas-apps/brocade-sannav-management-portal-tutorial.md @@ -96,7 +96,7 @@ Follow these steps to enable Microsoft Entra SSO in the Microsoft Entra admin ce > - **username**: Use the User Principal Name (UPN) format for SANnav usernames. While you can modify the username claim to suit your specific requirements, make sure the format complies with the standards outlined in the SANnav Management Portal User Guide. -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. +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. ![Screenshot shows the Certificate download link.](common/metadataxml.png "Certificate")