4 ms·
I suggest you investigate oAuth instead of rolling something yourself. That's how Google, Facebook, and Twitter solve this problem. Pick whichever version suits
by tantalor 13y ago
I suggest you investigate oAuth instead of rolling something yourself. That's how Google, Facebook, and Twitter solve this problem. Pick whichever version suits your needs,
http://oauth.net/core/1.0a/ http://oauth.net/core/1.0a/ (2009)
http://oauth.net/2/ http://oauth.net/2/ (2012)
- tonyhb 13y agoOut of all of these, I've always found the HMAC hashed request in OAuth 1 to make the most sense from a basic security point of view. The only concern being token refreshes.
- jlemoine 13y agoWe care a lot about the simplicity of our API. oauth adds too much complexity and does not fit well our use case (we don't need authentication).
- dmak 13y agoYou don't need to authenticate. You can use OAuth for just authorization: http://tools.ietf.org/html/rfc6749#section-1.3.2 http://tools.ietf.org/html/rfc6749#section-1.3.2
- jlemoine 13y agoBut this would reduce the ease of use of the API, increase the latency because of round-trip and will not provide a better security. The fit is not very good. oauth is a good standard when used for the correct use case, which is not the case for this. Sometime a simple solution is better than a framework