AkhilV.62094 (Customer) asked a question.
Hi team,
We have a group claims issue for OIDC app-Implicit Flow, when Okta is not generating token if user’s group claim exceeds 100.
Legacy Group claim we are using:
The Okta solution page ( https://support.okta.com/help/s/article/error-the-groups-claim-matched-too-many-groups-and-must-be-configured-to-match-fewer-groups?language=en_US ) suggests we split the tokens, but for that we need to use Token claims, instead of legacy which supports only one claim.
We tested Token claims with this expression: user.getGroups({‘group.type’: {‘OKTA_GROUP’}}, {‘group.profile.name’: {‘dcms’}}).![profile.name].
Now it turns out we can’t use the exact regex with the new tokens: https://support.okta.com/help/s/article/regex-expression-support-with-user-getgroups-function?language=en_US
Is there any way we can still use the regex (which is non-negotaible) and overcome the group number limitation?
Also we don’t have any group claims in auth server if that’s of any help.
Appreciate the support!
Hi @AkhilV.62094 (Customer) , Thank you for reaching out to the Okta Community!
This question is more appropriate for our dedicated Okta Developer Forum.
My advice would be to reach out via devforum.okta.com to take advantage of their expertise.
While we'll do our best to answer all of your questions here, this medium is more inclined towards Okta general questions around core products and features (non-custom/developer work).
While looking into this, it came to my attention that you have also posted there. Please continue the discussion with my colleagues on that thread.
Dropping the link to the thread here as well for anyone else in the community facing the same issue.
https://devforum.okta.com/t/legacy-group-claim-issue-implicit-flow/35363
Regards.
--
Help others in the community by liking or hitting Select as Best if this response helped you.
Collect them all. Learn a new skill and earn a new Okta Learning badge.
Just released: More Okta Community badges just added