Skip to main content

1.6.5

Released 4 Nov 2026

New​

  • PDF reports. The new Reports page downloads a PDF of the project — certificates and what expires soon, distribution problems, 47-day readiness and discovery — and can e-mail it daily, weekly or monthly through an SMTP notification channel. A report always contains only what its owner may see, and a project admin with access to the whole project can send it to other addresses too.
  • Single sign-on with OpenID Connect, SAML 2.0 and GitHub. Add any number of providers from a catalogue — Microsoft Entra ID, Google, Google Workspace, Okta, Keycloak, AD FS, Auth0, OneLogin, PingOne, PingFederate, GitHub, or a custom OIDC or SAML provider — where you type only a few values and the rest is read from the provider's discovery document or metadata. The sign-in page gets a button per provider and can route people by their work e-mail address.
  • Accounts and groups from the identity provider. A first sign-in can create the account with a default role, group memberships follow the groups the provider sends, and each provider can also require CertAutoPilot's two-factor authentication and sign the user out at the provider. A two-factor code an account enabled is asked at SSO sign-in too.
  • Test a provider before turning it on. Test connection checks the provider's settings, and Test sign-in signs you in at the provider and shows the claims it sent and what a real sign-in would do, without creating an account.
  • Move an account to another sign-in method. An owner can move a user between local password, LDAP and an SSO provider; roles and grants stay, and the group memberships the old method added are removed.
  • SSO sessions end on time. Each provider sets a session lifetime (12 hours by default) after which the user signs in at the identity provider again, and a change to how the provider judges sign-ins ends its open sessions at their next refresh.
  • Recover a locked-out installation from the command line. user reset-password can turn an LDAP or SSO owner into a local account and turn local password sign-in back on.
  • Quantum readiness per server, per source and over time. The page counts each server (address and port) once, by its weakest name, and adds a table per discovery source and the share of quantum-safe servers for the last 90 days.
  • Post-quantum certificate keys and ML-KEM alone are recognised. A certificate with an ML-DSA key is shown as Ready, and a server that negotiates ML-KEM without a classical part is shown as quantum-safe.
  • Servers that only accept RSA key exchange are scanned. They used to fail the scan; they now appear with their certificate as RSA (no PFS).
  • Probe key-exchange groups. A new opt-in check per discovery source tries every key-exchange group on its own and shows a server that supports a quantum-safe group but negotiates a classical one.
  • Notification when a server loses its quantum-safe key exchange. The new event discovery.kex_downgraded is sent once per server (one summary per source when there are more than five), also when the certificate was replaced in the same scan.

Changed behaviour​

Sign-in settings moved, and every account has exactly one sign-in method

LDAP and the two-factor policy are now on Settings → Sign-in. The password form signs an existing account in only through its own method: a local account is never checked against LDAP, and an LDAP account is never checked against a local password.

  • Local and LDAP sign-in can be turned off. With local sign-in off, organization owners with a local password can still sign in, and a change that would leave no owner able to sign in is refused.
  • Accounts are never merged by e-mail. An SSO sign-in whose username already belongs to another account is refused; move that account to the provider instead.
  • The LDAP bind password is stored encrypted. The plaintext copy is removed once every running node has been on 1.6.5 for a day; after a downgrade, re-enter the bind password on the LDAP page.
  • The last owner who can sign in without an identity provider cannot be removed. Demoting, deactivating, deleting or moving that owner is refused.
  • A notification channel's stored password or secret no longer follows a new destination. Changing an SMTP channel's server, port or TLS mode, or a webhook channel's URL, now requires entering the password, secret or bearer token again.
  • A session ends when its sign-in method goes away. Disabling a provider, turning local or LDAP sign-in off (or clearing the LDAP host), or moving an account to another method ends the affected sessions within 15 minutes; turning the provider on again does not bring them back.
  • A two-factor code works once. The same code, or an older one, is refused afterwards, so wait for the next code from the app.
  • Session refreshes are limited mainly per session. Each session may refresh 10 times a minute and one address 600 times, so a whole office behind one address no longer gets signed out, and a refused refresh keeps the session.
  • A successful token refresh is no longer an audit entry. Sign-ins, refused refreshes and token reuse are still recorded; a used refresh token is kept for 24 hours for reuse detection instead of 7 days.
  • LDAP sign-ins are bounded. One sign-in takes at most 20 seconds, and when a node already runs 16 at once the next one is answered "the directory is busy; try again".
  • Passwords are limited to 72 bytes. A longer one is refused with a clear message instead of a server error.
  • Quantum readiness counts servers, not endpoint rows. A server scanned under several names or by several sources used to count once per row, so the numbers on the page and the inventory card are lower than before.
  • A lost post-quantum key exchange is no longer sent as discovery.cert_changed. Rules that should still be told need the new discovery.kex_downgraded event.
Rolling upgrade

Turning local or LDAP sign-in off, enabling an SSO provider and starting a KEK rotation are refused until every running node is on 1.6.5, and a two-factor code is single-use only on 1.6.5 nodes. Going back to 1.6.4 turns local and LDAP sign-in on again, and SSO accounts can sign in there only after an owner sets them a password. Finish the upgrade of every node before using these features: a 1.6.4 node that comes back later ignores them.

Fixed​

  • Renew right after a certificate was issued now renews it. A Renew clicked while the issuance was still finishing answered "renewal already in progress" and nothing happened; it now queues the renewal, which starts once the issuance has finished.
  • Certificate requests no longer report a database read error as "not found". When the ACME account, AD CS connection or CA connection could not be read, creating a certificate said it did not exist; it now reports the read error.
  • Changing your own password no longer signs you out a few minutes later. Other sessions still end; the browser you changed it in keeps a new session.
  • Too many wrong two-factor codes now return to the password step. The sign-in page used to stay on the code field, where every further code was refused.
  • "Your session ended" is shown when an administrator ends a session. Moving, deactivating or resetting an account used to send its open browsers to the sign-in page without a word, and was logged as token reuse.