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
When using token auth, there should be an option to:
Use token used by the rest of the system vs. the custom token from nes
Apply normal hapi authentication to the upgrade
The current system requires an additional request that can be avoided by those who have everything they need already and also seems like it would loose authentication on reconnect. If able to specify custom auth headers from the client and auth strategy on the upgrade endpoint, both of these can be avoided when already using tokens elsewhere in the system.
The text was updated successfully, but these errors were encountered:
This thread has been automatically locked due to inactivity. Please open a new issue for related bugs or questions following the new issue template instructions.
lockbot
locked as resolved and limited conversation to collaborators
Jan 9, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When using token auth, there should be an option to:
The current system requires an additional request that can be avoided by those who have everything they need already and also seems like it would loose authentication on reconnect. If able to specify custom auth headers from the client and auth strategy on the upgrade endpoint, both of these can be avoided when already using tokens elsewhere in the system.
The text was updated successfully, but these errors were encountered: