This repository has been archived by the owner on Jan 8, 2024. It is now read-only.
internal/cli: waypoint login supports tokens #1848
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This builds on
waypoint login
introduced in #1831 for OIDC to provide a much nicer token-based login experience.Prior to this, users had to use
waypoint context create
and specifically had to use a login token with that. If they had an invite token, they first had to convert it usingwaypoint token exchange
. This is all friction and not obvious to users (though the underlying machinery is important).Users can now use
waypoint login
with just the server address and ANY token and the CLI automatically does the right thing. It checks if the token is an invite token and automatically exchanges it. It also infers all the TLS and server connection settings based on the hostname (same as OIDC).Demo
CleanShot.2021-07-13.at.10.55.13.mp4