cevoaustralia / aws-google-auth

Provides AWS STS credentials based on Google Apps SAML SSO auth (what a jumble!)
MIT License
537 stars 181 forks source link

Keep getting invalid password/username #183

Open ptonini opened 4 years ago

ptonini commented 4 years ago

Hello

I cant get credentials, no idea wy. User, password and AWS SAML app are ok: image

vishnu-axcess commented 4 years ago

I'm also facing same issue, but in my case this happens with a specific G-suit accounts I have tested with 3 different accounts out of which 2 accounts are giving this error on Ubuntu 18 and Amazon Linux2 but all 3 are working perfect on MACOS. All the systems are having same version aws-google-auth 0.0.35.

VShox commented 4 years ago

Same here. With the same debug log output Ubuntu 18.04, aws-google-auth 0.0.35 Was also tested on multiple mac machines and multiple google accounts 2FA is enabled

wryun commented 4 years ago

Works fine for me (Linux), failed on OSX for a new user account (worked fine with my login on the same computer). Maybe something to do with captcha.

VShox commented 4 years ago

Ok, after some debug I have more info:
I'm not sure what it depends on, but after hitting https://accounts.google.com/signin/v1/lookup I get back <Response [200]> then fall under # Handle the "old-style" page condition with passwd_challenge_url = https://accounts.google.com/signin/v1/lookup as was parsed from action form. The password was added to data, response came back as <Response [200]> with the page where error was parsed out as <span class="error-msg" id="errormsg_0_Email" role="alert"></span> what is technically should probably considered as no errors - empty span? but as the code has condition if error is not None: - it failed. Also in the code there is an attempt to parse out a captcha: cap = response_page.find('input', {'name': 'logincaptcha'}) AND on the page I got back there is a captcha BUT dom element has different name: identifier-captcha-input It might looks as google has one more auth way. The curious thing happened when I did clone the repo and ran the same under virtual environment - and surprisingly everything works! Though I did check code of repo vs. in-host version - everything is the same, I did check all used libs version - everything is the same. I did debug both versions in the same time - the requests, the bodies. the headers that both tools are sending are the same, but under virtual environment I got back 302 redirect with following Handling new-style login page and in-host version's behavior is explained above. Hope it will help, let me know if you would need more info.

omprakash1989 commented 4 years ago

I am facing the same issue here. Following @VShox steps (downloading and running) also did not resolve it. Anyone came up with a solution?

steliosfran commented 4 years ago

Same issue for me, I always get an Invalid username or password, tried with both 0.0.34 and 0.0.35.

I'm on macOS 10.14.6 if that makes any difference. 2FA is enabled and I'm not signed in to any other account on Chrome.

It only started happening a few days ago.

chhaviLife360 commented 4 years ago

I have the same issue. and am on the version 0.0.35. I always get Invalid username or password. I ma on macOS 10.14.5. Is anyone going to look at it? It is blocking me on some of my tasks.

netors commented 4 years ago

I have the same issue on 0.0.35 Mac 10.15.4. I have MFA enabled

VShox commented 4 years ago

Suddenly it started to work for me. I did not do much - played around with my 2FA, randomly set another default method, tried aws-google-auth - didn't work then did remove it, tried aws-google-auth again - didn't work, then came after half hour and tried aws-google-auth again - and suddenly it works.

tlvince commented 4 years ago

Duplicate of #179

dineshkumar181094 commented 4 years ago

Facing the same issue for user on mac it is working fine but on ubuntu getting same error.

maestrx commented 4 years ago

Having the same symptoms, also having 2FA enabled.