You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bug description
Error authenticating to IdP.: please install the driver (v1.45.1) and browsers first: %!w()
$ playwright --version
Version 1.49.1
To Reproduce
I am using playwright go, to run saml2aws - in order to connect to my Kubernetes cluster. I have already installed all necessary pre-requisite software (i.e. Chocolatey, Saml2Aws , Go software , Latest Playwright Go, Kubectl , AWS CLI etc).
However each time I am issuing the saml2aws commands (something like below, have hashed sensitive section), I keep getting same error. Tried different env.
saml2aws login --profile=******* --duo-mfa-option="Duo Push" --skip-prompt
Have anyone here in the community, come across similar problem and how they worked to get this resolved.
Not sure, what is forcing it to keep giving error around (v1.45.1) when I am already on latest version of 1.49.1
The text was updated successfully, but these errors were encountered:
Environments
Bug description
Error authenticating to IdP.: please install the driver (v1.45.1) and browsers first: %!w()
$ playwright --version
Version 1.49.1
To Reproduce
I am using playwright go, to run saml2aws - in order to connect to my Kubernetes cluster. I have already installed all necessary pre-requisite software (i.e. Chocolatey, Saml2Aws , Go software , Latest Playwright Go, Kubectl , AWS CLI etc).
However each time I am issuing the saml2aws commands (something like below, have hashed sensitive section), I keep getting same error. Tried different env.
saml2aws login --profile=******* --duo-mfa-option="Duo Push" --skip-prompt
Have anyone here in the community, come across similar problem and how they worked to get this resolved.
Not sure, what is forcing it to keep giving error around (v1.45.1) when I am already on latest version of 1.49.1
The text was updated successfully, but these errors were encountered: