Session and password policy
How long a sign-in stays good for your organization and its apps, how recent it must be for sensitive actions, and what your members' passwords must be — the five settings, the NATO and NIST AAL2 presets, and what users and apps see when a limit applies.
An organization administrator decides how long a sign-in stays good for the organization, and what a member's password must be. The settings are under Settings → Governance → Identity → Sessions and passwords. Every setting starts empty, which means no limit, so nothing changes until you set one.
The five settings
| Setting | Range | What it does |
|---|---|---|
| Maximum session age | 5 to 43 200 minutes (30 days) | This long after signing in, the person must sign in again before the organization or its apps open for them. |
| Idle limit | 5 to 1 440 minutes | After this long without using the organization, a new sign-in is required. Using another organization does not keep this one open. |
| Re-authentication for sensitive actions | 1 to 1 440 minutes | The actions below need a sign-in at least this recent. Unset, or longer than the deployment's own limit of 60 minutes, the 60 minutes apply. |
| Minimum password length | 12 to 128 characters | Applies whenever a member chooses a password. |
| Refuse passwords found in known data breaches | on or off | New passwords that appear in a breach corpus are refused. |
Only organization owners and administrators can change the settings. Each
change is recorded in the audit log as identity.policy.updated, with the
values before and after.
Presets
Two buttons fill in all five settings at once:
| Preset | Maximum age | Idle | Re-authentication | Password length | Breach check |
|---|---|---|---|---|---|
| NATO / government | 12 hours | 15 minutes | 15 minutes | 15 | on |
| NIST AAL2 | 12 hours | 30 minutes | 30 minutes | 15 | on |
A preset changes only these five settings. Your sign-in strength requirement and the email setting stay as you set them. Change any value afterwards and the Matches the … preset badge goes away; the settings themselves stay.
Fifteen characters is the NIST SP 800-63B minimum when a password is the only factor. If your organization requires two factors (Sign-in strength), you can lower it, but not below 12.
What a member sees
When a session is too old or idle
A session past the maximum age or the idle limit cannot open the organization. Switching to it answers Your session has expired for this organization. Sign in again to continue. The person's other organizations keep working. Signing in again starts a fresh session.
The limits are checked when the organization is opened, when a request names the organization or workspace it is for (a link, or the tenant-scope header), when an invitation to the organization or one of its workspaces is accepted, and on every sign-in to one of its apps. A page of the organization already open in the browser is not closed at the moment the limit passes; the limit applies the next time the organization is opened, the next request that names its scope, or an app signs in.
When an action needs a recent sign-in
A sensitive action with a sign-in older than the re-authentication setting is refused, and Scrydon asks the person to confirm it is them. The action is then sent again on its own; nothing has to be repeated. The sensitive actions are:
- listing your sessions, unlinking a sign-in method, and deleting your account without a password;
- changing the organization's identity policy: the sign-in strength floor, the session and password rules, the network rules and the end-user policy;
- rotating or retiring a signing key or a SAML signing certificate, and changing the certificates trusted for a sign-in provider;
- issuing, rotating or revoking a SCIM provisioning token;
- suspending a member, and making a member an admin (changing their role or inviting them as one);
- removing a verified domain;
- requesting or approving the recovery of a member's account.
The organization the action is for decides the age. Changing any other policy, or giving someone the member role, does not need a recent sign-in.
Confirming takes, in this order of preference:
- a passkey of the signed-in account, offered first when the person has one;
- the password, followed by the code from the authenticator app when the account has two-factor authentication turned on. An authenticator code on its own is not offered: it cannot renew the sign-in;
- sign in again, for an account with neither, or one whose second factor is sent by email. That ends the current session.
A passkey of a different account is refused: that sign-in is ended, and nothing is changed. After confirming, the person is back in the same organization, workspace and environment before the action is sent again. If that cannot be restored, the action is not sent.
When choosing a password
The minimum length and the breach check apply on every path that sets a password: sign-up through an invitation, a password change, a password reset and an administrator setting a member's password.
- A person who belongs to several organizations is held to the strictest of them, because one password opens all of them. The longest minimum applies, and the breach check runs when any of them requires it.
- At sign-up, the organizations that invited the address count.
- Passwords chosen before a setting changed are not checked again. A member meets a new minimum the next time they choose a password.
A password that is too short is refused with the length the organization requires: Your organization requires a password of at least 15 characters. A password found in a breach is refused with This password has appeared in a data breach. Choose a different one.
How the breach check works
Scrydon computes the password's SHA-1 hash and sends only its first five characters to a range service. The service answers with every hash it knows that starts with those five characters, padded so that the size of the answer says nothing, and Scrydon looks for the password's hash in that answer itself. The password and its hash never leave the platform.
By default the range service is
Pwned Passwords. Your operator can point
the deployment at a mirror instead, for example in an air-gapped installation
(auth.passwordBreachCheck.url, see the Helm reference).
If the range service cannot be reached, a new password is refused for members of an organization that requires the check, and the refusal is recorded in the audit log. Scrydon never accepts a password it could not check. The member can try again later. If the service stays unreachable, an administrator can turn the check off for the time being.
For your apps
The maximum age and the idle limit apply to apps that sign in with your organization's Scrydon account:
| Protocol | When the session is past a limit |
|---|---|
| OpenID Connect, interactive | The person is asked to sign in again before the app receives a code. |
OpenID Connect, prompt=none | The app receives login_required. |
| OpenID Connect, refresh token | The refresh is refused with invalid_grant. The app must send the person through sign-in again. |
| SAML | The person is sent to sign in again before an assertion is issued. |
Audit events
| Event | When |
|---|---|
identity.policy.updated | An administrator changed the policy. Records every field before and after. |
identity.session.limit_refused | A session was refused for its age, idle time or re-authentication age. Records which limit and where. |
identity.password.refused | A password was too short or found in a breach. Never records the password or its hash. |
identity.password.breach_check_unavailable | The breach check did not answer, and the password was refused. |