Add transparent SSO login support to ops#29
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
This PR adds transparent SSO support to the
opsCLI. When SSO is enabled in configuration,ops -loginuses OIDC device flow instead of prompting for local OpenServerless username/password credentials.Changes
ops config ssocommand support.AUTH/.wskpropsstate as legacy login.Validation
git diff --checkgo test ./...was not run locally becausegois not available in the current environment.Notes
The user-facing login command remains unchanged. SSO is selected from configuration/environment, so existing non-SSO workflows continue to work as before.