Description | This article describes how to identify Azure SAML groups when the portal displays fewer than 150 groups but authentication still fails. |
Scope | FortiGate, Azure SAML Authentication. |
Solution |
In some cases, the user groups displayed in the Azure portal do not align with those listed in SAML Authentication. This discrepancy occurs because the Azure portal does not display inherited (nested) groups.
samld_send_common_reply [95]: Attr: 10, 108, 'http://schemas.microsoft.com/ws/2008/06/identity/claims/groups' '8724203f-b372-4648-b9ae-8254d36cf736'
For example, the group 'chris top' may include two nested groups, 'chris' and 'chris1', but does not directly contain any users. As a result, the nested group memberships may not appear in the Azure portal but are still included in the SAML assertion.
To verify the total groups, including inherited ones, use the following commands in the Azure Cloud Shell:
Count the total groups (including nested groups):
List all groups the user belongs to:
View detailed information for a specific group (by Group Object ID):
These commands allow the retrieval of accurate group membership information, including nested groups, that may not be visible in the Azure portal.
Related article: |