Imagine an agency sharing a staging site with a client.
On Monday, the agency invites the client by email. On Friday, it removes them. The removal succeeds, but the client can still open the site.
Here is how that happens:
The agency removes the client. The Durable Object holding the site's access list records the change immediately.
The client's browser still has a signed Kinde token. The token remains valid until it expires. Kinde's default access token lifetime is 24 hours, and ending a session does not invalidate a token that has already been issued.
A nearby data center has a cached copy of the access decision: this client may open the site. That copy is up to 30 seconds old.
The client reloads the page. The gate finds the cached answer, trusts it, and grants access.
The token signature is valid. The cache is working as designed.…