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
Currently, Nomad UI supports logging in via an SSO if an ACL Auth Method is detected in the state store. Unauthenticated users are then presented with the following message:
And later when then click on either the auth method name or the Nomad ACL Token link, they are redirected to the following:
We will soon introduce a new auth method type, JWT, that does not require a redirect to a 3rd party provider, and in fact is just a string of characters much like the Nomad ACL Token. I see two possible ways we could address this in the UI:
Detect if the type of an ACL Auth Method is JWT or OIDC, and present a different dialog to the user depending on that, or:
Detect the shape of the token that is being pasted into the "Secret ID" text field. If it's JWT-shaped, call the /v1/acl/login endpoint, if it's not, treat it as a Nomad ACL Token.
The new /acl/login endpoint will expect an auth method name (just like the OIDC endpoint), and a token.
The text was updated successfully, but these errors were encountered:
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Currently, Nomad UI supports logging in via an SSO if an ACL Auth Method is detected in the state store. Unauthenticated users are then presented with the following message:
And later when then click on either the auth method name or the Nomad ACL Token link, they are redirected to the following:
We will soon introduce a new auth method type, JWT, that does not require a redirect to a 3rd party provider, and in fact is just a string of characters much like the Nomad ACL Token. I see two possible ways we could address this in the UI:
type
of an ACL Auth Method is JWT or OIDC, and present a different dialog to the user depending on that, or:/v1/acl/login
endpoint, if it's not, treat it as a Nomad ACL Token.The new
/acl/login
endpoint will expect an auth method name (just like the OIDC endpoint), and a token.The text was updated successfully, but these errors were encountered: