Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Auth0 not following oidc spec (again) (but in an other way) #136

Open
julien-leclercq opened this issue Oct 31, 2023 · 2 comments
Open

Auth0 not following oidc spec (again) (but in an other way) #136

julien-leclercq opened this issue Oct 31, 2023 · 2 comments

Comments

@julien-leclercq
Copy link

Hello,

As stated in the title, the /usreinfo endpoint returns a stringified epoch timestamp...
https://auth0.com/docs/api/authentication#user-profile

If you have any idea on how I could work around this other than hand making the request. Otherwise, do not bother, the problem is definitely on their side.

@ramosbugs
Copy link
Owner

Wonderful... you'd think Auth0 could at least be internally consistent with how they (mis)represent timestamps.

Fortunately, Auth0 appears to be returning raw JSON UserInfo responses rather than signed JWTs, so in this case I would suggest having an HTTP client shim that rewrites the /userinfo response to adhere to the spec (i.e., converts the string to a number) before returning it to this crate. You can pass a function that implements this shim directly to request[_async].

@julien-leclercq
Copy link
Author

Thanks, for now I have a dedicated reqwest client. might update later.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants