How to handle Oauth nonces on the server side?

I am writing part of the OAuth protocol provider on the server, and I am hacking my future into how many of the nonce sent by OAuth consumers I need to cache.

According to Twitter docs,

Twitter will only allow nonce to be used once by your application. Prevents repeated requests.

Question: My implementation will simply add all nonces received in memcached. But it will take up a lot of memory space. How much can I ideally cache and for how long?

+5
source share
1 answer

All Articles