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

Token support for cases such as SAML users on CG SaaS #64

Closed
rockspore opened this issue Aug 31, 2020 · 2 comments · Fixed by #66
Closed

Token support for cases such as SAML users on CG SaaS #64

rockspore opened this issue Aug 31, 2020 · 2 comments · Fixed by #66
Assignees

Comments

@rockspore
Copy link
Contributor

Currently, --token/-t is being described as Hybrid only. It should officially support cases such as SAML users on CG SaaS.

Background: Since the v1.1.0 release where the MFA for CG SaaS is being supported, the CLI will attempt to fetch an OAuth token based on the username/password (and a MFA token if needed) when --legacy is specified. This will prevent the user passed token from being applied.

@theganyo
Copy link
Member

theganyo commented Sep 1, 2020

@rockspore
Copy link
Contributor Author

Related: https://docs.apigee.com/api-platform/system-administration/enabling-saml-authentication-edge

Thanks! Based on the Get the machine user's OAuth2 tokens section, v1.0.0 definitely should work. And we just need to prevent the given token from being overwritten by MFA OAuth attempt, which will be a fairly simple fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants