saml2aws icon indicating copy to clipboard operation
saml2aws copied to clipboard

GoogleApps Login Broken in v2.24.0

Open johngrogg opened this issue 5 years ago • 11 comments

When trying to use v2.24.0 to log in via GoogleApps we receive the following error message:

error authenticating to IdP: page is missing saml assertion

Capturing the html pages we find it routes from the email entry page, to password entry page, then back to email entry.

Using v2.23.0 works without issue.

Looks like it might be related to #445

johngrogg avatar Mar 09 '20 18:03 johngrogg

So, this just started working again today 🤷‍♀️

purduemike avatar Mar 20 '20 18:03 purduemike

still broken for me, using v2.25.0

centur avatar Mar 23 '20 02:03 centur

@centur I'm running version 2.24.0, hopefully that works for you 🤞

purduemike avatar Mar 23 '20 19:03 purduemike

@purduemike Thanks, after some time-consuming fiddling I switched to aws-google-auth from Cevo

centur avatar Mar 23 '20 23:03 centur

ver 2.25.0 broken for me too but aws-google-auth works

error authenticating to IdP: page is missing saml assertion

lkolchin avatar Apr 03 '20 07:04 lkolchin

Quick update, now I can't reproduce the issue on any of the recent versions, 2.23.0, 2.24.0, or 2.25.0. All of them are now working for me.

johngrogg avatar Apr 03 '20 18:04 johngrogg

Currently looking at other SAML -> AWS cred solutions since ran into errors with the aws-google-auth documented here https://github.com/cevoaustralia/aws-google-auth/issues/184

Google seems to be random on who errors like this effects

jack1902 avatar Apr 22 '20 10:04 jack1902

Just fyI: - I was able to overcome this issue by removing 'Google Prompt' (note: I use an iPhone) and reverting back to Authenticator app in the Google Account I authenticate against.

paulieborg avatar May 07 '20 01:05 paulieborg

We started running into this exact issue in 2.26.1. After running saml2aws in debug mode, it looks like google is sending us to this page:

Screen Shot 2020-05-26 at 9

Im not sure if this is a condition that saml2aws can handle.

TheOutdoorProgrammer avatar May 26 '20 13:05 TheOutdoorProgrammer

It appears that going through https://accounts.google.com/DisplayUnlockCaptcha removes that screen and allows users to login again. So my gut feeling is that saml2aws cannot handle that condition.

TheOutdoorProgrammer avatar May 26 '20 14:05 TheOutdoorProgrammer

I was getting this issue on a recent version of saml2aws, the issue was that I had enabled "Use phone as a security key" as a 2SV method under my Google 2SV Settings. I removed that method and it fixed the issue.

danmoz avatar Oct 19 '22 19:10 danmoz