Auto account creation error with ADFS (OIDC): invalid SetHumanProfile.GivenName
🏬Self-hosted🔍Authentication🔗OIDC❓Question✅Solved
Hi team, thank you for the great work on ZITADEL!
I am currently setting up ZITADEL with an external OIDC provider (ADFS) and have enabled auto account creation. However, during the login/creation flow, I consistently encounter the following validation error:
What I've checked so far:
I synchronized with our ADFS administrator, and they confirmed that the given_name (or Givenname) claim is being returned properly in the token, and its value length is well within the 1–200 character range.
It seems like ZITADEL is either not receiving the claim under the expected key or failing to map it properly during the auto-creation request.
Questions:
Is there a way to inspect or deeply debug the raw token/claims that ZITADEL receives from the external IdP?
Any guidance on where to look in the logs or how to troubleshoot this further would be greatly appreciated. Thanks!
I am currently setting up ZITADEL with an external OIDC provider (ADFS) and have enabled auto account creation. However, during the login/creation flow, I consistently encounter the following validation error:
[invalid_argument] invalid AddHumanUserRequest.Profile: embedded message failed validation | caused by: invalid SetHumanProfile.GivenName: value length must be between 1 and 200 runes, inclusive[invalid_argument] invalid AddHumanUserRequest.Profile: embedded message failed validation | caused by: invalid SetHumanProfile.GivenName: value length must be between 1 and 200 runes, inclusiveWhat I've checked so far:
I synchronized with our ADFS administrator, and they confirmed that the given_name (or Givenname) claim is being returned properly in the token, and its value length is well within the 1–200 character range.
It seems like ZITADEL is either not receiving the claim under the expected key or failing to map it properly during the auto-creation request.
Questions:
Is there a way to inspect or deeply debug the raw token/claims that ZITADEL receives from the external IdP?
Any guidance on where to look in the logs or how to troubleshoot this further would be greatly appreciated. Thanks!
