3 ms·
Does this mean that your browser can cache the signed cert and log in to websites automatically without needing to even contact the provider again? I'm guessin
by StavrosK 14y ago
Does this mean that your browser can cache the signed cert and log in to websites automatically without needing to even contact the provider again?
I'm guessing there's some sort of timestamp there, to prevent someone from just stealing the cert and logging in to whatever they want as that user.
- marcioaguiar 14y agonot different from someone stealing your cookies.
- badida 14y agoYes, that is exactly right, and it's also why certs are short-lived (hours). When certs are renewed, the site the user plans on logging into is not revealed to the Identity Provider.
- brendn 14y agoBy my understanding, yes and yes. The third-party service caches the public key (with timestamp) and the browser caches the signed certificate (with timestamp). The timestamp gives the credentials a relatively short TTL to prevent a stolen cert from being used indefinitely.