Version Affected: 20.06 HF16, 21.04 HF11, 22.02 HF5, and 22.12 and later before 26.4.5
Bug Number: EE-4103
Bug Status: Closed - Fixed
Fixed in Version(s): 26.4.5 or later
Overview
On an OpenID Connect (OIDC) realm, a custom claim set to GroupList As Array on the Post Authentication tab is sent as a plain string in the ID token and the access token when the user is in only one group. When the user is in two or more groups, the same claim is sent as an array. Full Group DN List As Array behaves the same way.
A Service Provider that expects the claim to always be an array can fail to read the group of a user who is in only one group, so group-based access or role mapping fails for that user.
Cause
This is a known defect (EE-4103) in how the tokens are built. The claim is added to the token once for each of the user's groups. Several values are combined into an array, but a single value is written as a plain string, so the claim's format depends on how many groups the user is in. For example, for a claim named groups, a user in one group gets:
"groups": "ADMs"A user in several groups gets:
"groups": ["ADMs", "Group2", "Helpdesk", "VPN-Users"]EE-4103 also covers a related problem with the UserInfo endpoint, which returns only the user's first group. For details, see Bug: OIDC UserInfo Endpoint Returns Only the First Group for GroupList As Array Claims.
Resolution / Workaround
Upgrade to 26.4.5 or later to resolve this issue. From 26.4.5, the claim is sent as an array even when the user is in only one group.
Until you can upgrade, if the Service Provider can be changed, have it accept the claim as either a string or an array, and treat a string as a single group.
SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.
Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.
Comments
0 comments
Please sign in to leave a comment.