BadAuthentication

[khaberz]

I don't exactly know when it stopped working - there was a Debian Upgrade in that time which is a possible reason. I do get the following error now, which I can't figure out. Any Help is much appreciated. And thank you for this immensely helpful tool!

`
2023-06-15 14:27:37 configManager-INFO: validating configuration with schema './config.schema.yaml'

2023-06-15 14:27:37 configManager-INFO: schema validation passed 👍

2023-06-15 14:27:37 configManager-INFO: configuration validation passed 👍

2023-06-15 14:27:37 configManager-INFO: updated config: config.yaml

Traceback (most recent call last):
File "/home/khaberz/keep2todoist-main/app/app.py", line 152, in
keep.login(configManager.config['google_username'], configManager.config['google_password'], device_id='3ee9002270d00157')
File "/home/khaberz/keep2todoist-main/venv/lib/python3.11/site-packages/gkeepapi/init.py", line 697, in login
ret = auth.login(email, password, device_id)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/khaberz/keep2todoist-main/venv/lib/python3.11/site-packages/gkeepapi/init.py", line 62, in login
raise exception.LoginException(res.get("Error"), res.get("ErrorDetail"))
gkeepapi.exception.LoginException: ('BadAuthentication', None)`

[flecmart]

Hey,

I did not notice any changes in the authentication process for gkeepapi. Did you eventually enable 2FA recently, or changed your Google password? I would check the app password, maybe generate and try a new one.

[khaberz]

Thanks for your response. I have always has 2FA running, and that hasn't been a problem before. I have already tried a new app password as I had suspected something in there as well.
As part of the Debian-Upgrade I had to re-install the modules in the venv I have set up for this. Do you think any of those could cause the problem?
Thanks so much again!

[flecmart]

Hm, I guess it could be but it is hard to debug remotely. Are you able to try using the prebuilt docker image? This one ia always tested that all dependencies work together. khaberz ***@***.***> schrieb am Fr., 16. Juni 2023, 09:44:

…

Thanks for your response. I have always has 2FA running, and that hasn't been a problem before. I have already tried a new app password as I had suspected something in there as well. As part of the Debian-Upgrade I had to re-install the modules in the venv I have set up for this. Do you think any of those could cause the propblem? Thanks so much again! — Reply to this email directly, view it on GitHub <#29 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACNSHSYFSGLAPXH3ZYUXZRTXLQFEJANCNFSM6AAAAAAZH6IWE4> . You are receiving this because you modified the open/close state.Message ID: ***@***.***>

[sekrause]

I think this is triggered by the following bug, gpsoauth doesn't seem to be working correctly with OpenSSL 3: simon-weber/gpsoauth#48

That's why @khaberz had started having this problem after upgrading Debian: Bullseye uses OpenSSL 1.1.1, but Debian Bookworm ships OpenSSL 3.

The Docker container should be fine for now since it was last rebuilt two months ago with Bullseye, but the Dockerfile depends on python:3.9 which is now based on Bookworm. So the Docker container could have the same problem after the next rebuild. I think it might be a good idea so change the line FROM python:3.9 to FROM python:3.9-bullseye in the Dockerfile to stay on Bullseye as long as the OpenSSL 3 problem exists.

[khaberz]

Thanks @flecmart - The prebuilt Docker image works (after a small modification on calling the config.yaml, so in my case docker run -v **/home/khaberz/k2t/keep2todoist-1.3.1/app/**config.yaml:/app/config.yaml --restart always ghcr.io/flecmart/keep2todoist:latest - thanks @sekrause )

[flecmart]

Closed by #30 - thank you!