auth.expired

The caller was signed in, but the session or link has expired

Profile

Raised with

Status

401

Message

yours

Example

TS
return fail('auth.expired');
The caller gets
Terminal
HTTP 401

{
"ok": false,
"error": "Your session has expired. Sign in again.",
"code": "auth.expired"
}

Choosing between neighbours

Find the row that describes your case, and use the intent on the right.

  • If it is

    Use

  • The caller was signed in, but the session or link has expired

    auth.expired this page

Connections

Declared in the registry, both directions. Where an intent is used in your own code is something check and the gallery see; this site has no app code.

For registry authors

Starter intents. These are the intents prongs add errors puts in your registry, raised with fail(). Change the messages to suit your app, and the statuses through the status.* intents they are built from.

The entry prongs add errors writes into your registry. Change the message here, or the status through its status.* ref.

TS
'auth.expired': {
kind: 'semantic',
description: 'The caller was signed in, but the session or link has expired',
refs: ['status.unauthorized'],
binding: { publicMessage: 'Your session has expired. Sign in again.' },
},