-
Notifications
You must be signed in to change notification settings - Fork 20
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
Move OSM authentication to OAuth 2.0 #656
Comments
The least effort path forward might be resolving python-social-auth/social-core#758, then just use the new social auth backend. Otherwise, this could mean finding a different authentication plugin. |
I'll work on this. |
I'd like to clarify that the OSM Wikidata matcher does not currently use an OAuth library for authentication. A few years ago, a deliberate decision was made to move away from using Sorry if the documentation is out of date. |
I take that back. I'm using the requests-oauthlib Python library. |
osm-wikidata/matcher/osm_oauth.py Line 12 in 2a5ace3
Note, cc: @EdwardBetts |
Passing-by to record that OSM-OAuth2 support has been recently merged into Out of curiosity, which were those project-specific limitations that made |
@n1ngu Thanks for your comment! I don't remember what problem I had with I'll take another look. |
OAuth 1.0a is deprecated, and programs which use it to authenticate requests to OpenStreetMap should move to OAuth 2.0. A date has not yet been set for turning off OAuth 1.0a and HTTP Basic.
It's best to move to OAuth 2.0 well in advance of any turn-off, because users may take some time to upgrade software and to re-authenticate.
See openstreetmap/operations#867 for details.
The text was updated successfully, but these errors were encountered: