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

Authentication #11

Open
zdne opened this issue Aug 14, 2013 · 14 comments
Open

Authentication #11

zdne opened this issue Aug 14, 2013 · 14 comments

Comments

@zdne
Copy link
Contributor

zdne commented Aug 14, 2013

Direct support for API authentication.

RFC proposals

@xurde
Copy link

xurde commented Aug 14, 2013

This sounds really useful to me.

@zdne
Copy link
Contributor Author

zdne commented Aug 14, 2013

@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?

@rurounijones
Copy link

I would be interested in supporting OAuth 1.1 which requires setting HTTP Authorization header with various fields.

@remkoboschker
Copy link

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.

@kadishmal
Copy link

OAuth 2.0 is quite widely used.

@zdne zdne mentioned this issue Oct 29, 2013
@zdne zdne mentioned this issue Dec 17, 2013
@zdne
Copy link
Contributor Author

zdne commented Dec 17, 2013

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

@zdne
Copy link
Contributor Author

zdne commented Jan 31, 2014

To be addressed (and closed) with #47.

Baggz pushed a commit that referenced this issue Feb 26, 2014
@zdne zdne assigned zdne and unassigned zdne Jul 2, 2014
@w3irdrobot
Copy link

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 {?apikey} is in all requests without having to manually add it as parameters to all paths.

@zdne
Copy link
Contributor Author

zdne commented Dec 18, 2014

Hey @searsaw,
yes, this is our top-priority – scheduled right after #25 (which is drawing to an end so we will hopefully start on it soon).

cc @pksunkara

@netmilk
Copy link
Contributor

netmilk commented May 11, 2015

The oauthd project has a very nice gallery of declarative descriptions for various OAuth authentications of more than 100+ production APIs. Have a look to files conf.json and settings.json in any folder here.

I think it's a good inspiration for OAuth requirements in the API Blueprint syntax.

@pksunkara
Copy link
Contributor

Syntax proposed at #201

@zdne
Copy link
Contributor Author

zdne commented Dec 1, 2015

Added RFC proposals to the OP: #11 (comment)

@imanel
Copy link

imanel commented Feb 22, 2018

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?

@hsluoyz
Copy link

hsluoyz commented Dec 11, 2020

Any update?

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

10 participants