-
Notifications
You must be signed in to change notification settings - Fork 101
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
Add support for OAuth 2.0 authentication flows #284
Comments
@jirutka Given that we don't support plugins yet, I think we could add auth types that people find useful. Do you know of any CLI tool that supports OAuth 2.0? I know there are a couple of OAuth HTTPie plugins, but they differ from your proposed implementation. |
I don’t know about any, that’s basically the reason why I’d like to add it into xh. |
In general we try to be compatible with HTTPie. Similar issue for HTTPie (currently empty): httpie/cli#1427 For reference, this OAuth 1.0 plugin exists (and is listed in the official docs): https://github.com/qcif/httpie-oauth1 While it's ugly I think we'd want to go for the same approach of cramming everything inside the A popular OAuth 2.0 crate exists: https://lib.rs/crates/yup-oauth2 |
It was just an example, I don’t insist on that choice of options at all. :)
This is not suitable, it provides just the ‘device’, ‘service account’ and ‘installed’ authorization flows, not client_credentials nor authorization_code. |
Can you please consider adding support for OAuth 2.0, at least the client_credentials grant?
Example:
The text was updated successfully, but these errors were encountered: