-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Authentication #11
Comments
This sounds really useful to me. |
@xurde Glad to hear that! If you feel like, feel free to propose a syntax or just share a stub / example of how would you like to describe it. Also are you interested in a particular type of authentication? |
I would be interested in supporting OAuth 1.1 which requires setting HTTP Authorization header with various fields. |
I would like to be able to mock / use / define the requesting of a token based on username/credentials and using that token for subsequent requests to the api. I suppose inlining some javascript that generates / parses the tokens or the username/credenitials into the blueprint could be a solution. |
OAuth 2.0 is quite widely used. |
Please let me know whether traits as proposed in #47 would improve auth needs. Also refer to this example: https://gist.github.com/zdne/01e287fe18d232672d43#file-4-example-gist-fox-api-md |
To be addressed (and closed) with #47. |
Not sure if this is still being worked on, but a way to document that an API key is required for all requests would be great! So somewhere I could put that |
Hey @searsaw, cc @pksunkara |
Syntax proposed at #201 |
Added RFC proposals to the OP: #11 (comment) |
So what's the status of authentication? #201 was closed, because it was superseded by apiaryio/api-blueprint-rfcs#5 and apiaryio/api-blueprint-rfcs#6. They were merged as RFC over two years ago, so is it going to be implemented? |
Any update? |
Direct support for API authentication.
RFC proposals
The text was updated successfully, but these errors were encountered: