Closed akshay196 closed 2 years ago
Thanks for reporting! I would see to reproduce this before we make changes. Is a free tier on auth0 enough to reproduce?
Thanks for reporting! I would see to reproduce this before we make changes. Is a free tier on auth0 enough to reproduce?
Yes. I have been using basic starter plan of Auth0 with no cost.
That is strange, I thought we have an explicit workaround for that!
Any idea why that's not working?
Ah yeah, the problem is that the int is formatted into a string here:
Preflight checklist
Describe the bug
When trying to login in with Auth0 provider, getting internal error and not able to login. The error is
reason:json: cannot unmarshal string into Go struct field Claims.updated_at of type int64
, check below for full stack trace. It seems Unmarshaling to Claims failed due tostring
type of update_at. Also noticed the issue is already fixed in #609, but I don't understand why we are converting the correct int64 type of udpatedAt back to string (which might be the cause of this error). I am happy to contribute to fix this.Reproducing the bug
Steps to reproduce the behavior:
Relevant log output
Relevant configuration
Version
kratos:v0.9.0-alpha.3
On which operating system are you observing this issue?
Linux
In which environment are you deploying?
Docker Compose
Additional Context
No response