Operations
These guides are for the people who run SSOGEN after it is set up: reading and exporting the audit log, sending events to other systems, storing secrets, trusting certificates, checking health, and backing up and upgrading safely.
- Audit log
Read the audit log, verify its hash chain, seal the daily checkpoint and export it for auditors.
- APIs and automation
Which API to use for scripts, provisioning and sign-in, and how to call the Automation API.
- Webhooks
Send events to a receiver, verify the signature on every delivery, rotate the secret and resume a suspended receiver.
- Secrets
Store, replace and delete the passwords and tokens SSOGEN uses, and rotate the key that protects them.
- Trusted certificates
Make SSOGEN trust your company certificate authority so LDAPS directories connect.
- System health
The System health page, the Setup health checklist, the Logs page and the health check endpoints.
- Backup and upgrade
What to back up, why a database backup alone is not enough, and the order to upgrade.
- Branding and admin roles
Put your name, logo and colors on the sign-in pages, and control who administers SSOGEN with six built-in roles.
- Admin lockout protection
How SSOGEN refuses a change that would leave nobody able to sign in to the Admin Console, and how to recover.
- Operator security notes
How SSOGEN keeps passwords, codes and tokens out of your logs, and the server settings to leave alone.
- Audit event reference
The events SSOGEN writes to its audit log, grouped by area, with when each one is recorded, the fields every event carries, and how to export or forward them.
- Break-glass recovery of an administrator
The command that hands the Admin Console back when an administrator is locked out: when to use it, how to run it, what it changes, what it records in the
- Error codes
The SSOGEN error codes an employee, administrator or operator can meet, grouped by where they appear, with what each one means and what to do.
- Release notes
What the latest SSOGEN release brings for customers, and what to know before you upgrade.
- Reverse proxy and TLS requirements
What a reverse proxy or load balancer in front of SSOGEN must do and must not do: the Host header, TLS versions and ciphers, certificates, the client-address
- Version compatibility
Which versions of SSOGEN, the Gateway, the Web Agent and the Authenticator work together, the operating systems, Java and PostgreSQL each one supports, and