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

Support for Oauth 1.0 #46

Closed
IvanGoncharov opened this issue Mar 17, 2016 · 5 comments
Closed

Support for Oauth 1.0 #46

IvanGoncharov opened this issue Mar 17, 2016 · 5 comments

Comments

@IvanGoncharov
Copy link
Member

Suggested by @sanchojaf on Gitter:

we know OAuth 1.0 is not supported by Swagger 2.0, is possible and make sense add to patch.yaml ?

@maryguirola
Copy link
Contributor

Hi, these APIs use OAuth 1.0 authentication:

  1. thenounproject
  2. audiosear.ch
  3. slideroom

@IvanGoncharov
Copy link
Member Author

@maryguirola Thank you. It's very helpful.

@maryguirola
Copy link
Contributor

@IvanGoncharov You're welcome.

@MikeRalphson
Copy link
Collaborator

@maryguirola One possible way to represent oAuth1 is to declare a securityDefinition of:

{
"type": "apiKey",
"in": "header",
"name": "Authorization",
"description": "oAuth1"
}

It would be up to the client to negotiate oAuth1 and build the Authorization header 'manually'. I'm thinking of doing something similar for Amazon AWS's HMAC security scheme.

@MikeRalphson
Copy link
Collaborator

See OAI/OpenAPI-Specification#61

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

No branches or pull requests

3 participants