heitorlisboa
Guardian JWT is generated with the wrong time
I’m building an authentication API using Phoenix, Guardian and Bcrypt, but I’m having an issue with the time present on the tokens generated by Guardian. At the same time the token was generated, my validation on the front-end was saying that the token was already expired.
To investigate, I headed to jwt.io and decoded the token that I was receiving, and saw that both the iat (issued at) and exp (expiration time) were more than 3 hours behind the time when the token was generated.
However, I noticed that if I verify this token on the same API right after generating it, it says the token is valid. That probably means that my entire Phoenix app is using the wrong time. Is there a way to fix that?
Marked As Solved
BartOtten
Have you checked the time of the server/system you run the API on?
iex > Time.utc_now()
If it is off, the fix depends on your operating system.
Also Liked
heitorlisboa
You’re right. I just checked and noticed that the problem is that I’m using Ubuntu via WSL on Windows and its time is not synced with my main operating system. I ran the command you said on both my Windows and Ubuntu terminals and they were not the same.
Now I just need to find a way to sync both systems. Thanks a lot!
Popular in Questions
Other popular topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
We build reliable cloud platforms for business-critical systems.
Categories:
Sub Categories:
Forums
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Develop your skills with books, videos, and courses.
Producing high quality Elixir screencasts since 2017.
Enabling companies to succeed by building software people love.
Courses that'll move you from confusion to "Aha, now I get it!"