4 ms·
If it's your software generating the tokens, then that means they'd need the shared key, or private key in order to sign the token... which is already a problem
by tracker1 10y ago
If it's your software generating the tokens, then that means they'd need the shared key, or private key in order to sign the token... which is already a problem. Now if you're accepting tokens from a third party, that's another issue, and should be much more constrained.
I go farther still and require a VERY short expiration on service to service requests (documented as 1m, coded as 2m) which combined with https limits the chance of replay attacks.