You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use OIDC provider which in order, uses SAML and somehow, in the email_verified field there is a same email as in email. Since its not a boolean, SDK fails to parse the response.
Thank you for bringing this issue to our attention.
We've reviewed the details and based on our analysis, it seems unusual. According to the SDK schema, the field is defined as a Boolean. Given that the SDK is behaving as expected, the issue may not be related to the SDK itself.
Since we are unable to reproduce the issue, can you please define steps to reproduce the issue if still persists.
@tanya732 Thank you for taking a look! With saml it's possible to map some fields of the saml response into the final get user response. That happens on the enterprise level, so it's not something common. But my point is that instead of failing the entire parsing in this case, sdk can ignore such fields, as right now I have to reimplement the entire client to call the endpoint.
Checklist
Description
We use OIDC provider which in order, uses SAML and somehow, in the
email_verified
field there is a same email as inemail
. Since its not a boolean, SDK fails to parse the response.Would be nice to have some kind of a workaround for this case
Reproduction
Additional context
No response
auth0-java version
2.10.0
Java version
21
The text was updated successfully, but these errors were encountered: