Skip to content
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

OAuth2 authorize URL extra params + Google example #114

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

mccahill
Copy link

...to illustrate using extra parameters

Google seems to like having a scope parameter specified in the Oauth2 authorize URL, so I added an extra parameters option to the description. There is also a working example of using OAuth2 against one of the Google Calendar APIs

Signed-off-by: Mark McCahill [email protected]

…or Google Calendar to illustrate using extra parameters

Google seems to like having a scope parameter specified in the Oauth2 authorize URL, so I added an extra parameters option to the description. There is also a working example of using OAuth2 against one of the Google Calendar APIs

Signed-off-by: Mark McCahill <[email protected]>
@phairow
Copy link
Contributor

phairow commented Oct 9, 2014

this looks like a good addition. it's been around a little while but it seems like a good thing to merge with a few modifications. I'd think the parameter should be configurable for both authorize and access_token. I'm going to have to double check if we need permission to add the google definition.

Here's an example of some additions :

  "oauth":{
     "options":{
        "authorize":{
           "scope": "read, write, execute"
        },
        "access_token": {
            "redirect_uri": "http://example.com/theuri"
        }
     }
  }

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants