-
Notifications
You must be signed in to change notification settings - Fork 606
Closed
Labels
help wantedIndicates that a maintainer wants help on an issue or pull requestIndicates that a maintainer wants help on an issue or pull request
Description
Hello!
I've been using saml2aws for quite a while now. Updated to 2.36.19 this morning.
I use the Browser provider, but now I'm getting this error: (personal info redacted, obviously)
# saml2aws login --config=/Users/ssilvidi/.aws/saml2aws_default -a default --credential-process --profile default --verbose
DEBU[0000] Running command=login
DEBU[0000] Check if creds exist. command=login
DEBU[0000] ensureConfigExists filename=/Users/ssilvidi/.aws/saml2aws_default_creds pkg=awsconfig
Using IdP Account default to access Browser https://accounts.google.com/o/saml2/initsso?idpid=xxxxx&spid=yyyyy&forceauthn=false
DEBU[0000] Get credentials helper=osxkeychain serverURL="https://accounts.google.com/o/saml2/initsso?idpid=xxxxx&spid=yyyyy&forceauthn=false"
DEBU[0000] Get credentials helper=osxkeychain user=ssilvidi
DEBU[0000] building provider command=login idpAccount="account {\n URL: https://accounts.google.com/o/saml2/initsso?idpid=xxxxx&spid=yyyyy&forceauthn=false\n Username: ssilvidi\n Provider: Browser\n MFA: Auto\n SkipVerify: false\n AmazonWebservicesURN: urn:amazon:webservices\n SessionDuration: 28800\n Profile: default\n RoleARN: arn:aws:iam::01234567890:role/GoogleApps\n Region: us-east-1\n}"
Authenticating as ssilvidi ...
could not install driver: could not install driver: could not check if driver is up2date: could not run driver: signal: killed
Error authenticating to IdP.
github.com/versent/saml2aws/v2/cmd/saml2aws/commands.Login
github.com/versent/saml2aws/v2/cmd/saml2aws/commands/login.go:108
main.main
github.com/versent/saml2aws/v2/cmd/saml2aws/main.go:199
runtime.main
runtime/proc.go:283
runtime.goexit
runtime/asm_arm64.s:1223
I already had download_browser_driver = true in my config, but I've tried each method (env var and cli) just to test, and they all return the same error.
I also created a new test configuration (saml2aws configure -a test), in case my method has something outdated in it, but I get the same error on login.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
help wantedIndicates that a maintainer wants help on an issue or pull requestIndicates that a maintainer wants help on an issue or pull request