Sign-in methods
How people sign in to Scrydon (password, email link or code, authenticator app, passkey, and a smart card or other certificate), how strong each sign-in counts, and how to turn on certificate sign-in for your organization.
The methods, and how strong each one counts
Your organization's sign-in floor and the apps that sign in through Scrydon read the strength of each sign-in.
| Method | Strength |
|---|---|
| Password, email link, email code | single factor |
| Password plus an authenticator app or a backup code | two factors |
| Passkey | phishing-resistant |
| Smart card (certificate, complete mode) | phishing-resistant |
| Certificate (first factor mode) | single factor; your floor asks for a passkey or authenticator next |
Certificate sign-in
People sign in with a certificate their card or device holds: a PIV or CAC smart card, a national eID card, or a certificate your organization's own PKI issued. The browser shows its certificate prompt (and, for a card, asks for the PIN). No password is involved.
Certificate sign-in works for accounts your organization manages, so you need a verified domain first.
It is for organizations whose identity provider is Scrydon itself. If your domain requires SSO through another identity provider, certificate sign-in is refused there like any other sign-in that skips it.
Turn it on
Under Settings → Platform → Identity → Certificates, an owner or admin:
- Adds your trust anchors: the CA certificates (PEM) your users' certificates are issued under. A root or an issuing CA both work. Only certificates that chain to one of your anchors are accepted.
- Chooses the mode:
- Complete, for smart cards: the key is on the card and the PIN unlocks it. You also name the certificate policy OIDs your PKI puts on those certificates (for PIV, its hardware policies); a certificate without one of them is refused. A complete sign-in counts as phishing-resistant, and your apps (and Microsoft Entra, when your domain signs in to Microsoft 365 through Scrydon) see it as multi-factor.
- First factor, for certificates stored as files: the sign-in counts as one factor, and a raised sign-in floor then asks for a passkey or authenticator.
- Chooses the identifier that ties a certificate to a person:
- UPN (the default): the user principal name in the certificate. PIV/CAC cards and certificates Microsoft Entra issues carry it.
- National identifier: the
serialNumberof the certificate's subject, which national eID cards carry. Scrydon never stores it: it keeps only a keyed fingerprint, so the number itself cannot be read back. Your deployment's operator has to configure the key before you can choose this.
- Switches it on.
Link a certificate to a person
A certificate signs in only once it is linked to an account:
- an owner or admin opens the person under Settings → Organization → Members, and in the Account section adds their UPN or national identifier; or
- the person links the certificate they hold, from Account → Security → Certificates. They need to have signed in with two factors or a passkey in the last 10 minutes; a certificate cannot link itself.
Every link and unlink is in the Audit Log.
What is checked at every sign-in
- The certificate chains to one of your anchors, every signature is valid, and nothing on the chain is expired, signed with SHA-1, or an RSA key under 2048 bits.
- The certificate is allowed for client authentication.
- Revocation: Scrydon asks the CA's OCSP responder, or reads its CRL. If neither answers, or the answer is not signed or not current, the sign-in is refused. A certificate revoked after an answer was cached can sign in until that answer expires, at most an hour.
- The linked account is managed by your organization and is not suspended.
Any refusal shows the person the same message. The Audit Log records why, naming only the certificate's subject and issuer (without their serial number attribute).
For your deployment's operator
Certificate sign-in runs on its own hostname, for example
certificate.auth.example.org, which the TLS client certificate reaches
directly. Scrydon does not accept a certificate a proxy forwards in a header.
The operator enables it in the chart; see
auth.certificateSignIn in the Helm reference.
API
Under the authentication service, for the session's active organization (owner or admin):
| Method and path | Does |
|---|---|
GET, POST /sso-extensions/certificate/settings | read or set { enabled, mode, identifier, requiredPolicyOids } |
GET, POST, DELETE /sso-extensions/certificate/anchors | list, add ({ pem }), remove a trust anchor |
GET, POST, DELETE /sso-extensions/managed-accounts/:userId/certificate-bindings | list, add ({ value }), remove a person's link |
Errors carry a code: certificate_anchor_invalid,
certificate_policy_oids_required, certificate_national_id_key_missing,
certificate_no_verified_domain, certificate_sign_in_not_enabled,
certificate_identifier_bound (that identifier is already linked to someone),
certificate_session_too_weak (linking your own certificate needs a recent
two-factor or passkey sign-in), and certificate_refused for a sign-in.