PingCastle Enterprise settings overview
PingCastle Enterprise groups its configuration options into sections on Configuration > Settings. This page links each section to its documentation.
Authentication
See Configuring Authentication for PingCastle Enterprise for the full setup guide, including these methods:
- Local authentication
- Windows authentication
- OpenID Connect
- SAML2 authentication
- Header authentication
- Client certificate authentication
- Custom login message
- Login options
Administration
- Licensing — PingCastle Enterprise License explains the per-user licensing model and the legacy per-domain licensing model, along with the Licensing screen's status display and license upload.
- Data retention — Data Retention
- Notifications — Configuring the web host and Configuring reminders and the weekly report
- Email — Configuring Email for PingCastle Enterprise
- Scanning and Scheduling — Scanning and Scheduling; see also Active Directory scan scheduling for how PingCastle Enterprise uses these settings
- Action Plans — Action Plans
- Provisioning — Provisioning
System
- Database — Shows the database engine, connection string, detection status, app pool identity, detected schemas, total domain count, and last data update, all read-only. The Active schema dropdown shows the schema PingCastle Enterprise uses and is the only editable setting on this screen — use it to force a specific schema when multiple schemas are active. Changing it requires a restart.
- Security — Antiforgery protection and Password rate limiting
- Logging — Log levels, File logging, and Downloading logs
- Application — Application
Entra Scanner
See Entra Scanner for the settings synced from the Entra Scanner microservice. See Entra scanning for the scanning feature itself.
Configuration migration from appsettings.Production.json
In previous versions, PingCastle Enterprise stored configuration settings in appsettings.Production.json. Starting with version 4.0, PingCastle Enterprise stores these settings in the database instead.
When you start the application for the first time after upgrading to version 4.0, PingCastle Enterprise automatically migrates the settings from appsettings.Production.json into the database. You don't need to manually port any values from the old file.
As part of this migration, the installer backs up the original appsettings.Production.json file to a config-backups/ subfolder in the install directory. Reference this backup if you need to verify a setting after the upgrade.