Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upCannot verify JWT at all?? #177
Comments
|
Can you please provide your Ruby version and jwt version you are using? After my upgrade to macOS Sierra I had to re-install all my brew packages including rbenv. |
|
Sure! Ruby 2.3.1 Yeah, thought that OpenSSL might be messed up now or something. What was the problem you were having? |
|
Yey, I got it to work like this: Was trying it before with |
|
Ah, ok. The password was the issue. The password isn't base64 encoded when creating a token with this gem. It needs to be plain text. |
|
This is actually a problem with Auth0's quickstart documentation. Hope they update it soon :) |
Hi everyone,
we are evaluating Auth0 for our service and have problems to get going.
We can verify the token we get on
jwt.ioas you can see here:However in the console I get the following:
I copied the values from the console into the webpage. So I am pretty confident that they are actually the same.
What can be the problem? Should I reinstall Ruby after my upgrade to macOS Sierra?