-
-
Notifications
You must be signed in to change notification settings - Fork 421
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
support for urn:ietf:wg:oauth:2.0:oob ? #280
Comments
Hrm. Is that a bearer token of some form, or does it get converted into one in some part of an oauth dance? Do you have a specification for how this should work? |
The value in the title of the ticket here is the redirect URL. This may mainly be a documentation issue; I eventually figured out that the thing to do when using this flow (the "other" application flow in Google's terminology) was instead of specifying |
Oh, yes, that's definitely a documentation issue. =( |
On the other hand, I'd argue that all of OAuth has a documentation issue. |
@glyph You can also do it like this, I have not used it with gmail but I it is much better then pasting the ?code={somecode} into your actual python code.
|
@sigurdurb I tried your method, gives me an exception like |
I'm not sure which project this belongs in a request on, but:
urn:ietf:wg:oauth:2.0:oob is a special redirect URL that indicates to some providers (google in particular) that the token code should be presented to the user so that it can be copied and pasted into (e.g.) a command-line tool.
It doesn't seem like there's anywhere to put this token value once copied.
The text was updated successfully, but these errors were encountered: