You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I am using hapi-io in an auth: { mode: 'try' } environment. This means I have many routes that need authentication, but also some that don't need any.
I've added a new option to hapi-io called authModeTry (default false) which - when user authentication fails - feeds back false to hapi instead the error message authentication failed.
I will now try to add the pull request (first time, so I hope I get everything right).
The text was updated successfully, but these errors were encountered:
You can simply omit the auth option when registering the hapi-io plugin. No authentication will be required to establish a socket.io connection, and authentication will still run on a per route basis.
I'll update the README to indicate that the auth option is optional.
No it didn't help. If I omit "auth" option, I'd need to add auth strategy to dozens of routes, which is very cumbersome. Even more when I have set up the normal react app to just use auth: { mode:"try" }
Hello, I am using hapi-io in an
auth: { mode: 'try' }
environment. This means I have many routes that need authentication, but also some that don't need any.I've added a new option to hapi-io called
authModeTry
(defaultfalse
) which - when user authentication fails - feeds backfalse
to hapi instead the error messageauthentication failed
.I will now try to add the pull request (first time, so I hope I get everything right).
The text was updated successfully, but these errors were encountered: