[openspending-dev] api key

[Nick Stenning]

> see this "Ideas" issue: https://github.com/okfn/ideas/issues/43 (Cross-OKF single-signup (for api kesy)  

Yep. As suggested below, it's not immediately obvious to me that there's really a need for a shared process for issuing/checking API keys. It's typically only a few lines of code, and is usually much easier to get right than the standard litany of password reset, email login links, etc etc.  

One possible benefit might be centralised measurement of usage of said API keys, but I think there are better ways of doing that anyway (statsd/graphite) which themselves have next to zero integration overhead (well, statsd, anyway...)

-N
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/openspending-dev/attachments/20130909/6ba27921/attachment.html>