Skip to content
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

Allow any authentication method when using token auth #5

Closed
kpdecker opened this issue Sep 4, 2015 · 0 comments
Assignees
Labels
Milestone

Comments

@kpdecker
Copy link
Contributor

@kpdecker kpdecker commented Sep 4, 2015

When using token auth, there should be an option to:

  1. Use token used by the rest of the system vs. the custom token from nes
  2. 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.