2 ms·
> you want to be able to revoke auth straight away if an account is compromised It really depends on the system. In my experience, there are tons of apps that
by mooreds 1y ago
> you want to be able to revoke auth straight away if an account is compromised
It really depends on the system. In my experience, there are tons of apps that want to be able to revoke access but weigh that against transparent re-authentication. OIDC handles both nicely with:
* short access/id token lifetimes (seconds to minutes)
* regular transparent refreshes of those tokens (using a refresh token that is good for days to months)
This flexibility lets developers use the same technology for banks (with a shorter lifetime for both access/id tokens and refresh tokens) and consumer applications (with a short lifetime for access/id tokens and a longer lifetime for refresh tokens).
- afiori 1y agoImho the complexity and cost of having super short-lived access tokens is worse than eating up 1 more per-request db lookup