unable to locate IDP authentication form submit URL

[babanjot]

Hello team
I am using keycloak as an identity broker and google as an Identity Provider. While using saml2aws for AWS CLI login, I am facing this issue
unable to locate IDP authentication form submit URL
I have used IDP initiated URL as the URL to set up my profile.
Here is the verbose output of my login

babanjot@babanjot:~/Downloads$ saml2aws --verbose login
DEBU[0000] Running                                       command=login
DEBU[0000] check if Creds Exist                          command=login
DEBU[0000] Expand                                        name=/home/babanjot/.aws/credentials pkg=awsconfig
DEBU[0000] resolveSymlink                                name=/home/babanjot/.aws/credentials pkg=awsconfig
DEBU[0000] ensureConfigExists                            filename=/home/babanjot/.aws/credentials pkg=awsconfig
Using IDP Account default to access KeyCloak https://**********t/auth/realms/aws-accounts-sso/protocol/saml/clients/***********
To use saved password just hit enter.
? Username babanjot@tothenew.com
? Password **********

DEBU[0013] building provider                             command=login idpAccount="account {\n  URL: https://***********t/auth/realms/aws-accounts-sso/protocol/saml/clients/**********\n  Username: babanjot@gmail.com\n  Provider: KeyCloak\n  MFA: Auto\n  SkipVerify: false\n  AmazonWebservicesURN: urn:amazon:webservices\n  SessionDuration: 3600\n  Profile: saml\n  RoleARN: \n  Region: \n}"
Authenticating as babanjot@tothenew.com ...
DEBU[0015] HTTP Req                                      URL="https://accounts.google.com/signin/v1/lookup" http=client method=POST
DEBU[0015] HTTP Res                                      Status="200 OK" http=client
unable to locate IDP authentication form submit URL

[rohanpower]

Getting the same issue using AzureAD as IdP

[GMartinez-Sisti]

It's a missleading error.

I got that error after I changed my password while using --skip-prompt. After performing a login and specifying the password I confirmed that the keychain entry was updated (MacOS) and it started working again without the need to input the password.