-
Notifications
You must be signed in to change notification settings - Fork 126
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
Regression: request.auth.isAuthenticated is true and request.auth.credentials is {} when user not logged in #111
Comments
Thanks very much for reporting this @alanshaw can you give us a bit more detail as to the circumstance/context where this is happening in your app so we can create a regression test and fix this. |
I will submit a test when I get a sec... |
Sweet. thanks! 👍 |
In the mean time I rolled back to v5.1.0 |
Makes sense. |
Both auth modes 'optional' and 'try' fail the test for |
Good question @alanshaw . ❓ |
atOrAbove was missing, the first (and only) affected version was 5.1.1 Also, the summary was incorrect. Refs: https://nodesecurity.io/advisories/81 Refs: dwyl/hapi-auth-jwt2#111
atOrAbove was missing, the first (and only) affected version was 5.1.1 Also, the summary was incorrect. Refs: https://nodesecurity.io/advisories/81 Refs: dwyl/hapi-auth-jwt2#111
atOrAbove was missing, the first (and only) affected version was 5.1.1 Also, the summary was incorrect. Refs: https://nodesecurity.io/advisories/81 Refs: dwyl/hapi-auth-jwt2#111
With the latest version of the plugin my
mode: 'try'
routes exhibit this behaviour.This did not happen previously.
The text was updated successfully, but these errors were encountered: