ContentsThe library

Proving Who You Are

Making Somebody Stop Being Signed In

Last timeRequests You Did Not Make

Access lives in more places than anybody remembers. This lesson inventories them, orders the revocation, verifies it landed, and names the window during which it has not.

Everywhere access lives

Somebody is dismissed at four in the afternoon and their access must stop.

This is the test of everything in the course, and it is failed far more

often by incomplete inventory than by missing mechanism.

Write the list out. Not the list of systems, the list of places where a

decision about this person is currently held.

FIG 1The inventory, and whether revocation lands at once
you can delete it directrevocation lands immediait expires on its own clusually on the first dra
browser sessions in your1101
access tokens already is0011
refresh tokens1101
third-party grants you i1101
long-lived keys for scri1101
cached permission lookup0010
a grant held at an exter0100
a signed cookie in a par0010
The fourth column is the finding. The first five rows are what people write down; the last three are what gets missed, and two of them are marked because they are the rows where nothing you do has any effect and you can only wait. A revocation procedure that does not name those rows is incomplete rather than wrong.

Three entries deserve specific attention because they are routinely

forgotten. Long-lived keys issued for scripts and integrations, which

belong to a person who has now left and which no session logic touches.

Cached authorisation decisions inside services, which are correct and stale

for as long as their own lifetime. And grants at external providers, where

the person signed in to a third-party tool with your account and that tool

holds a refresh token you have no record of.

The order to do it in

The sequence matters, and getting it wrong is how a careful operator ends

up with a system that reissues what they just deleted.

The lesson stops here

5 more paragraphs to go

You have read the opening. The rest of the argument, the problems that check whether it landed, and the lines worth keeping at the end all come with a plan.

The first lesson of every course in the library reads the whole way through, free, so you can see exactly what the rest of them are.

See the planThe contents

This is the reading half

Starting the course gives you your own copy of it. Every idea on every page has problems standing under it, marked with a reason rather than a tick, and any sentence you do not believe can be opened and argued with. None of that can happen on a page nobody owns.

The contents

The rest of this course

  1. 01Who You Are, What You May Do, and Who Remembers
  2. 02What Each Kind of Proof Actually Resistsopening only
  3. 03The Thing the Browser Carriesopening only
  4. 04The Token That Answers for Itselfopening only
  5. 05Two Tokens Beat Oneopening only
  6. 06Borrowing Somebody Elses Proofopening only
  7. 07The Request Your Browser Sent for Somebody Elseopening only
  8. 08Making Somebody Stop Being Signed Inyou are here

Read alongside