We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We are currently using saml2aws with Browser provider to achieve this - would be nice to have proper integration
The text was updated successfully, but these errors were encountered:
Can you share the setup you have with the browser?
Sorry, something went wrong.
[default] name = default app_id = url = `https://OURSTARTURL.awsapps.com/start/#/saml/default/SAML_APP/ins-CODE` username = DEV_NAME provider = Browser mfa = Auto mfa_ip_address = skip_verify = false timeout = 0 aws_urn = urn:amazon:webservices aws_session_duration = 3600 aws_profile = AWS_SSO_PROFILE #(from ~/.aws/config) resource_id = subdomain = role_arn = region = http_attempts_count = http_retry_delay = credentials_file = saml_cache = false saml_cache_file = target_url = disable_remember_device = false disable_sessions = false download_browser_driver = false headless = false prompter =
Saml2aws starts browser session (chromium on mac) which is used to login to aws sso first, and then proceeds to switch to SAML.
Customer's account is set up as SAML application in AWS SSO (NOT a part of the organisation).
Frankly, after reviewing this, we dropped it in favour of cross-account trust relationship and sts-assume-role instead.
No branches or pull requests
We are currently using saml2aws with Browser provider to achieve this - would be nice to have proper integration
The text was updated successfully, but these errors were encountered: