Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Configuration

Every setting below is planned: no code reads any of them yet. The table fixes the intended behaviour and defaults so that operators and later releases agree. It mirrors the architecture view of configuration; a value marked “open question” is not yet decided.

SettingDefaultStatus
accepted certificate issuersopen questionplanned
registry repository locationnone; requiredplanned
index databasenone; required, disposableplanned
waiting window for recovery and disable requests48 hoursplanned
authorisation code lifetime60 seconds, single use, PKCE (S256) requiredplanned
ID token lifetime5 minutesplanned
access token lifetime10 minutes, sender-constrained (RFC 8705 mTLS or RFC 9449 DPoP)planned
refresh tokenrotated on every use; idle limit 7 days; absolute limit 30 days, never past the login certificate’s expiryplanned
CA revocation re-checkat every login and every token refreshplanned
cached OCSP/CRL answer reuseuntil its nextUpdate, at most 1 hour; no fresh answer means refusalplanned

The token values follow the OAuth 2.0 Security Best Current Practice (RFC 9700). The index database can be deleted at any time: it is rebuilt from the registry repository.