Re: [rest-discuss] API Keys
- Hi Erlend,
On Nov 29, 2012, at 12:26 PM, Erlend Hamnaberg <ngarthl@...> wrote:
> Is there anyone with experiences with implementing API Keys in their apis?
If you are looking for something along the lines of OAuth Client identifiers, you should take a look at OAuth 1 and 2 and the associated discussions.
Eran IMO is the go-to guy in that space and you should get much out of his blog
and recent projects
https://github.com/hueniverse/hawk (The README should provide a very good start).
Looking at Amazon IAM, as already suggested, is also good:
Here are good intro docs from Google:
Personally, I am most excited about OZ, because Eran's OAuth 2 criticism looks very valid when you dig into it.
> Putting the APIKey in the URI is obviously a bad idea as that leaks to every cache and intermediary. Including Apache logs.
> So it must be a new header field.
> The problem with APIKeys as such is that they are spoofable, unless they are crypographically protected somehow, so my question is:
> What do you do in your api?
> I am thinking about writing up an internet draft for a new Api-Key header field.
- On 29 Nov 2012, at 12:55, Cíat Ó Gáibhtheacháin <k@...> wrote:
you'd end up with something similar to
Digest auth, so you might want to consider just using that unless you
can come up with something provably superior. Here's an example of an
alternative auth method:
http://www.xml.com/pub/a/2003/12/17/dive.htmlAnd here's another:http://tools.ietf.org/html/draft-shanks-http-form-authentication-00
My first I-D, posted this week. :)
- On Thu, Nov 29, 2012 at 5:55 AM, Cíat Ó Gáibhtheacháin <k@...> wrote:
> You'd be better off proposing an alternative HTTP auth method, if+1, HTTP auth is a tragically underused part of the standard.
> anything, where the client sends something like this (assuming the API
> key is a UUID):
> Authorization: Key b67570be-3a22-11e2-8ca6-0015c55d83ee