-
Notifications
You must be signed in to change notification settings - Fork 457
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
HS256 not supported #30
Comments
Hi @namel Which sample in particular did you get the error in? |
it was on 01-Login |
Did you make any changes to the config in the |
No I did not. After applying the workaround described above, I'm now getting an error that the token is signed in the future, even though my time is set automatically over the network. This could be related do my environment though? I'm on the Linux Subsystem for Windows. Another thing that fails on this environment is that the uniqid package fails (see microsoft/WSL#468) |
for issues with system clocks you can add the auth0 = new auth0.WebAuth({
// ...
leeway: 5
}); |
Also can you check which "Client Type" you have set in the clients settings in the Auth0 dashboard? |
@namel choosing single-page-app in "Client Type" solved my problem |
Yes!! To solve |
Why does this work? |
authentication fails, console indicates error:
"invalid_token" "Algorithm HS256 is not supported. (Expected algs: [RS256])"
I found a workaround to this on issue: auth0/auth0.js#303
but since this is a sample app, it should work right out-of-the-box
The text was updated successfully, but these errors were encountered: