Open MaybeOron opened 2 years ago
I have the same problem (3 hours instead of 8) with the latest version of saml2aws, using Google as Identity Provider. @MaybeOron Did you find out a solution?
I have the same problem (3 hours instead of 8) with the latest version of saml2aws, using Google as Identity Provider. @MaybeOron Did you find out a solution?
My problem was the Session Duration set up in Google
I transfered to aws sso
I transfered to aws sso
Because you resolved the problem with AWS SSO, you can close this issue. :wave:
please help me understand what is wrong, saml2aws + jumpcloud, max session duration configured to be 12 hours, but gets a 6 hours session instead, AWS roles are configured for max session of 12 hours, cant use --session-duration=43200 with a higher value obviously.
saml2aws commands:
saml2aws configure \ --idp-provider JumpCloud --session-duration=43200 \ --username $username -r $aws_region \ --mfa=Auto --profile=$aws_user_type \ --url $url \ --skip-prompt