-
Notifications
You must be signed in to change notification settings - Fork 178
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stopped working circa 4/10/2020 #179
Comments
We are having the same issue. |
I have the same issue, i believe the captcha screens have changed. |
When you're not letting me in, I know I am not the only one... |
A couple of days earlier it stopped working for me with Google responding that browser doesn't support JS. #160 (comment)_ |
Grrr - this type of issue sux - I've created a new branch that can store all html that comes back from google see #181 If we can get some HTML we can see if this can help fix the issue. |
Hi Steve, I have some HTML that has been generated. I need time to scrub the files for my IDP ID, etc, but the material error seems to be this:
I will scrub my HTML results here in a bit and get them up here in the event that this is a red herring. Also, thinking ahead and assuming that maybe Google is enforcing a JS-enabled browser, how hard would it be to just move this part of the authentication to the browser such that the JS requirement is happy? Regards, -R.
|
They are wrapped with triple backticks. I guess it's just so large that the parser is breaking down: |
Here is the second of two files from accounts.google.com-o-saml2-initssofalse.html:
|
@sinkr could you please adjust your comments and wrap the html in triple backtick instead of single backtick? It'll help with readability. |
👍 I am experiencing the same issue. |
Fixed the code embed - will need to take a deeper look later, but worrying that they are moving to processing some security in the browser. There seem to be an increasing number of these reports. |
Is it possible to have this part done on the browser? |
Enhancing on what I proposed, could this flow be applied? Example app: Seems like a more robust way to have this feature working. Unless I am missing something critical. |
Was able to get past this issue by doing the following:
|
Hmm, I've had awscli v2 installed this whole time. I think it might be where you are in the rotation of being presented with a CAPTCHA by Google, based on what I think I read on this thread. |
I'm experiencing this as well. Here are the versions I'm running on
|
I've been hit by this also, so I've started working on a fix by modifying the code directly inside Eventually I cloned the repository to do my work here. I made a virtual environment, installed the project and its dependencies with TL;DR: as a workaround and before a fix is released, installing urllib3 1.25.8 (i.e. |
As I can now use AWS I've got more urgent things to do, sorry lads, but feel free to check and use my changes to the codebase so far here (it's not functional yet): master...ramnes:fix-google-captcha |
Installing urllib3==1.25.8 doesn't help me :( |
It's not going to help to resolve this issue but if anyone is blocked because of that, in the meantime there's this Chrome extension extracting the credentials from the browser: https://chrome.google.com/webstore/detail/saml-to-aws-sts-keys-conv/ekniobabpcnfjgfbphhcolcinmnbehde?hl=en I'll try the urllib update on my side too |
I've tried to apply changes that @ramnes made, but unfortunately, it doesn't help me. Now the captcha is showing me but some another error is blocking me |
It's not going to check my captcha and printing the same error - "Invalid username or password" |
Just did a git clone of @ramnes repo and |
It returns me HTML page after I passing the captcha
|
Yes, it's a debug from my WIP branch. You should not try to run it. As I said, it's not functional yet. |
Yep, it is 1.25.8 now |
Same issue, upgrading urllib3 didnt fix anything |
Related discussions and alternative approaches that are worth taking a look: |
Removal/adding of
last free lines. |
I don't even have the |
@saada In this case you can try to config it manually into your
If you can login successfully, the param It's working for me this way... |
It doesn't help. |
My team and I have moved over to https://github.com/ruimarinho/gsts since this achieves the same goal. |
I moved to gsts as well and it works well. Thanks |
Manually adding a profile which these options fixed the issue for me. |
I saw that the user @ramnes (Thanks mate) created a pull request resolving the conflict in captcha request but still continue to receive authentication errors, after a few hours of debugging I discovered that you cannot send the password together with the captcha, first you need to pass the captcha and after that it redirect you (301) to the password authentication page. I changed the code to include this new request and everything worked again. I've created a pull request for that. Please feel free to ask any question :) |
@brunodasilvalenga's fix worked for me. Here's how you can use it: git clone https://github.com/brunodasilvalenga/aws-google-auth.git
cd aws-google-auth
git checkout fix-google-captcha
pip install -e . --user |
fwiw @brunodasilvalenga's branch did not work for me, still get the javascript error page |
Which one @dgccdna ?? |
Just cloned this branch and did a |
but I mean which error are you getting? |
@brunodasilvalenga sorry, also didn't realize I switched accounts between issues, this one: #184 (comment) |
Hey @dgccdna . I don't reckon that problem that you're having is the same that I solved :(( |
I figured it was different but the other ticket was closed as a duplicate
and was hoping I was wrong. Maybe we should reopen it?
My problem only happens with one of my accounts, unfortunately the one with
more usage. I don't get captcha prompts, just this Javascript error page.
Maybe there's an anti csrf thing missing?
…On Fri, May 1, 2020, 10:48 PM Bruno da Silva Valenga < ***@***.***> wrote:
Hey @dgccdna <https://github.com/dgccdna> . I don't reckon that problem
that you're having is the same that I solved :((
Maybe this step is not cover by the package yet. It's happen because
google does changes every time and I was wondering some of could be just a
test A/B because is not everyone is getting the same issue with you. Try to
debug the code and doing the same steps manually using a Rest API Client
like Insomnia or postman.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#179 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AOWARSEOUKRGOM7SH4ZTDO3RPOX3RANCNFSM4MFVUYTA>
.
|
Hey @brunodasilvalenga The pull request work for me initially. However after some time i am getting an error while running any command - Starting aws-google-auth again reset the expiration for another one hour but the commands are still not working and showing the above error. Looking into .aws i can see config.lock, credentials.lock and saml_cache.lock files along with normal files. Should i try removing .aws folder?? i have tried using --no-cache option. |
Confirmed this one worked for me. Thanks! |
Hey @mandeep-bal I also encountered this after my initial token expired. I just went to .aws/config and removed |
@brunodasilvalenga's PR fixed the problem for us: #179 (comment) |
When will @brunodasilvalenga‘s PR get merged? |
Merged and released as part of |
Awesome! Thanks @stevemac007 |
Some people get
Invalid username or password
.I get:
ERROR:root:'NoneType' object has no attribute 'get' Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/aws_google_auth-0.0.34-py3.7.egg/aws_google_auth/__init__.py", line 75, in cli process_auth(args, config) File "/usr/local/lib/python3.7/site-packages/aws_google_auth-0.0.34-py3.7.egg/aws_google_auth/__init__.py", line 222, in process_auth google_client.do_login() File "/usr/local/lib/python3.7/site-packages/aws_google_auth-0.0.34-py3.7.egg/aws_google_auth/google.py", line 235, in do_login passwd_challenge_url = 'https://accounts.google.com' + form.get('action') AttributeError: 'NoneType' object has no attribute 'get'
Passwords are verified correct, I've tried no cache, I've tried adding a new account, and I've tried resetting my Google password all to no avail.
It looks like Google changed something. Let me know how I can help diagnose it.
The text was updated successfully, but these errors were encountered: