-
Notifications
You must be signed in to change notification settings - Fork 112
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
Clarification on use of OAuth 1 vs 2 #2
Comments
Correct; OAuth 2 requires SSL when used in most modes. It can be used in MAC mode, however that usage is not yet standardised, so we can't use it. Thanks for the feedback; I'll clarify this in the documentation. |
When can we expect to see OAuth 2 support? Is this in the works? |
+1 for OAuth 2 support. |
+1 as well for OAuth 2 support. |
OAuth2 is not currently in the works by the REST API team due to the HTTPS requirement, we are trying to focus on the solutions that work for (virtually) all WordPress sites, however I do encourage any contributors to work on an oauth2 plugin :) |
I had a look over the spec but couldn't see any explicit discussion about why version 1 of the protocol was chosen over v2. The closest I saw to an explanation was this line:
Which I presume is hinting that you can't rely on all sites having SSL to protect v2's secret credentials?
The text was updated successfully, but these errors were encountered: