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
It would be helpful if a URL can be specified (using an env var) which is used to obtain the token. Ideally then use the username and password provided via --auth=.
The token fetch and use sequence would then be triggered upon response header Www-Authenticate:, which also typically contains keyword JWT or Bearer to indicate which prefix was expected.
The text was updated successfully, but these errors were encountered:
@jayvdb I'm not sure if we should include this into the plugin. Do you know any other similar mechanism from other plugins? I doubt that it is out of this plugin scope, maybe you can create another wrapper or lib from this plugin instead?
The primary difference is that ntlm and kerberos know the 'endpoint' where they can convert user/pass to get the tokens needed. For JWT, that endpoint could be anywhere on the same host.
I understand if you still would rather that this plugin doesnt attempt this, in which case I'll try to build my own.
It would be helpful if a URL can be specified (using an env var) which is used to obtain the token. Ideally then use the username and password provided via
--auth=
.The token fetch and use sequence would then be triggered upon response header
Www-Authenticate:
, which also typically contains keywordJWT
orBearer
to indicate which prefix was expected.The text was updated successfully, but these errors were encountered: