Skip to content
All guides
Authentication and SSO4 min read

The developer’s guide to auth sessions

The useful frame is not "is this secure" but "what does an attacker get if this one thing goes wrong, and how quickly would we know".

The useful frame is not "is this secure" but "what does an attacker get if this one thing goes wrong, and how quickly would we know".

This piece walks through how we think about it at Paycux, what we have changed our minds about, and where the sharp edges are.

Sessions 101

Sessions 101 is where this gets concrete. Detection beats prevention when prevention is uncertain. If you cannot stop a class of abuse outright, make sure it produces a signal loud enough that someone sees it the same day.

Rotate on a schedule, not on an incident. A rotation path that has been exercised is a routine change; one that has never been used is an outage waiting for the worst possible moment.

Sessions and 3rd party auth providers

Sessions and 3rd party auth providers is where this gets concrete. Rotate on a schedule, not on an incident. A rotation path that has been exercised is a routine change; one that has never been used is an outage waiting for the worst possible moment.

Detection beats prevention when prevention is uncertain. If you cannot stop a class of abuse outright, make sure it produces a signal loud enough that someone sees it the same day.

  • Scope credentials to the smallest useful blast radius
  • Alert on the abuse you cannot prevent
  • Exercise the rotation path before you need it
  • Log the decision, not just the outcome

Sessions and security

That brings us to sessions and security. Detection beats prevention when prevention is uncertain. If you cannot stop a class of abuse outright, make sure it produces a signal loud enough that someone sees it the same day.

Detection beats prevention when prevention is uncertain. If you cannot stop a class of abuse outright, make sure it produces a signal loud enough that someone sees it the same day.

Use secure attributes on your cookies

Use secure attributes on your cookies is where this gets concrete. Rotate on a schedule, not on an incident. A rotation path that has been exercised is a routine change; one that has never been used is an outage waiting for the worst possible moment.

Rotate on a schedule, not on an incident. A rotation path that has been exercised is a routine change; one that has never been used is an outage waiting for the worst possible moment.

Blast radius is the metric that actually matters.

Tie session information to user information

Tie session information to user information is where this gets concrete. Detection beats prevention when prevention is uncertain. If you cannot stop a class of abuse outright, make sure it produces a signal loud enough that someone sees it the same day.

Blast radius is the metric that actually matters. A credential that can read one organization's data is an incident; the same credential scoped to every organization is a company-ending event, and the difference is a design decision made months earlier.

Further Reading:

Further Reading: deserves its own treatment. Blast radius is the metric that actually matters. A credential that can read one organization's data is an incident; the same credential scoped to every organization is a company-ending event, and the difference is a design decision made months earlier.

Blast radius is the metric that actually matters. A credential that can read one organization's data is an incident; the same credential scoped to every organization is a company-ending event, and the difference is a design decision made months earlier.

Authentication vs. authorization

Consider authentication vs. authorization. Detection beats prevention when prevention is uncertain. If you cannot stop a class of abuse outright, make sure it produces a signal loud enough that someone sees it the same day.

Blast radius is the metric that actually matters. A credential that can read one organization's data is an incident; the same credential scoped to every organization is a company-ending event, and the difference is a design decision made months earlier.

Where this leaves us

If there is one thing worth taking away, it is that the expensive decisions are the ones made implicitly. Making them on purpose costs an afternoon.

If you are working through the same problem and want to compare notes, the docs cover the mechanics and the console shows the behaviour on your own data.

Everything here, already built

Sign-in, enterprise SSO, directory provisioning, roles and an audit trail behind one API.

Stop reading, start shipping

The quickstart takes about ten minutes and leaves you with a working sign-in.