Skip to content

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