amr claim as string breaks OIDC IdP integration — PR #855 open

🌟Contribution❌Unsolved➕Feature Request👟Actions🔗OIDC

Hey, we're integrating Zitadel (v4.12.1, self-hosted) with an external OIDC provider and hitting a blocker. Their IdP returns the amramr claim as a string ("amr": "pwd""amr": "pwd") instead of an array ("amr": ["pwd"]"amr": ["pwd"]). This breaks the oidc library's JSON unmarshaling since TokenClaims.amrTokenClaims.amr is typed as []string[]string.

Error: json: cannot unmarshal string into Go struct field itcAlias.TokenClaims.amr of type []stringjson: cannot unmarshal string into Go struct field itcAlias.TokenClaims.amr of type []string

They won't change it on their end and Actions can't help since parsing fails before any hook fires. I would love to solve this with a custom Action if you had any options to do so.

I've opened PR #855 on zitadel/oidc to fix this. Would be great to get a review and understand the timeline for getting it into a Zitadel release. It's currently blocking our adoption of Zitadel completely.

Link: https://github.com/zitadel/oidc/pull/855

Thanks!