Intermittent "401 Client Error: Unauthorized for url..." issue

[tamakisquare]

First of all, I want to be clear that, IMO, this issue isn't caused by Pyrebase but lies with one of Pyrebase's dependencies, oauth2client. I have already filed an issue with oauth2client's github. I am also reporting it here as it also impacts the Pyrebase project, like in my case.

@thisbejim, any thoughts on this issue? Is there a way to get around it in Pyrebase?

Python version: 3.4.3
Pyrebase version: 3.0.25
Service account is used

[thisbejim]

Thanks for opening this issue @tamakisquare! This is a great find and the issue you filed on the oauth2client repo is really nicely detailed about what is actually happening here. I don't have any insights into this at the moment but will take a look when I get the time.

Oh and have a happy new year!

[tamakisquare]

Thanks, @thisbejim.

I have applied a fix to my local copy of the oauth2client library. It's been running fine for several days. Trying to put the fix in as a pull request to the oauth2client project but I am having trouble passing the existing set of tests of the project prior to applying the fix, so that task is on a pause for now.

Meanwhile, I believe the issue will likely trigger people reporting random 401 errors symptom to the Pyrebase project, so I want to make sure you and the other Pyrebase users are aware of this issue.

Thanks for your new year wishes, my friend. Wish you a journey full of joy in the new year. And thank you for the great work on Pyrebase. It has saved me a great deal of time trying to integrate my system with Firebase. Cheers.

[theacodes]

Heads up, we're actively working to replace oauth2client with google-auth. Switching would allow this library to also move away from httplib2.

Are y'all open to moving to a new auth library? If so, can you let me know if google-auth is missing any specific features you need?

[tamakisquare]

@jonparrott, the link to google-auth in your message is not accessible. I tried to search for it on Github but couldn't find it. Is google-auth the name of the repo?

I have not been involved in the development of Pyrebase, so @thisbejim would be the one to answer your questions.

[theacodes]

@tamakisquare my apologies, it's https://google-auth.readthedocs.io

[arpwal]

This is another reason why the path to oauth2client isn't working out for you @tamakisquare
https://google-auth.readthedocs.io/en/latest/oauth2client-deprecation.html

[arpwal]

@thisbejim any updates yet on making the transition to google-auth?

[heston]

I know this issue is a little old, but I was running into the same thing, and thought I would try upgrading the oauth2client dependency to google-auth.

Here's the PR: #249

As far as I can tell, everything works (unit tests, plus manual QA on other untested methods).

I'd appreciate a review from @thisbejim, or another maintainer. Thanks!

[theacodes]

I'm also happy to take a look (as the author of both of those auth libraries)

[heston]

Update on #249: I left a db stream running overnight, with the google-auth changes. I see that the stream successfully refreshed the oauth2 token several times without encountering a 401 response. Very encouraging!

[rawmean]

Please consider merging with master. This is a big problem and you seem to have the solution.