-
Notifications
You must be signed in to change notification settings - Fork 110
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
Unable to use programmatic_auth not possible #59
Comments
I googled around for the programmatic_auth issue, it seems to be some known issue with the hangouts API (as described in the hangups issue #260). Please be advised that only APIs in https://github.com/Byron/google-apis-rs are supported. I wonder whether it might be easier for you to just do the HTTP requests yourself? w.r.t. the scope divider, I fixed this. |
Found that out too after that, Sadly I am stuck to googles page "Cookies are ot enabled" :/ |
oh, and I looked after the scope separation; the official documentation uses |
hm oh thats interesting because in there fromular on the login page they use a plus :/ Sorry for the missleading |
@dermesser quick question. Is there a way to get the url that the dialog prints to a variable so that I can use that url in a request? |
@dermesser basicly I mean how can I get the response of the |
if you really want to go that route, you can supply Authenticator::new() (https://github.com/dermesser/yup-oauth2/blob/master/src/authenticator.rs#L73) with a delegate (https://github.com/dermesser/yup-oauth2/blob/master/src/authenticator_delegate.rs#L62) that captures the verification_url. |
Thanks. Reason is I have to use (sadly) programmatic_auth for hangouts because hangouts uses a oauth1.0 scope which is only allowed via programmatic_auth but I want still to use your crate :) so I have to intercept it a little bit |
Using
programmatic_auth
as auth_uri it failes to generate a correct URL.redirect_uri
andresponse_type
aren't allowed but they get added usingFlowType::InstalledInteractive
.Google says
Parameter not allowed for this message type: redirect_uri
andParameter not allowed for this message type: response_type
also the scopes need to be devided by a
+
instead of spaces.After that it would be nice to get the code which is in the cookie "oauth_token".
This is needed for generating the correct token for using the hangouts chat api (see hangups). Idea is to do automatic logins/auths. 100% from CLI
Did I miss something?
The text was updated successfully, but these errors were encountered: