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 · 1 comment
Closed

Allow any authentication method when using token auth #5

kpdecker opened this issue Sep 4, 2015 · 1 comment
Assignees
Labels
feature New functionality or improvement
Milestone

Comments

@kpdecker
Copy link
Contributor

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.

@hueniverse hueniverse self-assigned this Sep 4, 2015
@hueniverse hueniverse modified the milestone: 0.3.0 Sep 4, 2015
@Marsup Marsup added feature New functionality or improvement and removed request labels Sep 20, 2019
@lock
Copy link

lock bot commented Jan 9, 2020

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.

@lock lock bot locked as resolved and limited conversation to collaborators Jan 9, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature New functionality or improvement
Projects
None yet
Development

No branches or pull requests

3 participants