--- title: General settings description: The General Settings window lets you change some general system-wide settings for your PingFederate servers. component: pingfederate version: 13.1 page_id: pingfederate:administrators_reference_guide:pf_general_settings canonical_url: https://docs.pingidentity.com/pingfederate/13.1/administrators_reference_guide/pf_general_settings.html llms_txt: https://docs.pingidentity.com/pingfederate/llms.txt docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md revdate: March 10, 2026 section_ids: about-this-task: About this task steps: Steps --- # General settings The **General Settings** window lets you change some general system-wide settings for your PingFederate servers. ## About this task The settings in this window are independent of one another. ## Steps 1. Go to **System > Server > General Settings**. 2. Change any of the following settings: * To turn off automatic multi-connection error checking, select the **Disable Automatic Connection Validation** checkbox. This checkbox is cleared by default. Learn more in [Configuring automatic connection validation](pf_configuring_automatic_connection_validation.html). * To turn off automatic identity provider (IdP) *(tooltip: \
\

A service that manages identity information and provides authentication services to relying clients or SPs within a federated or distributed network.\

\
)* adapter validation, select **Disable IdP Adapter Validation**. This checkbox is cleared by default. Learn more in [Disabling automatic IdP adapter validation](pf_disabling_automatic_idp_adapter_validation.html). * To override the verbosity of runtime transaction logging for all identity provider connections, select an option on the **IdP Connection Transaction Logging Override** menu. The default setting is **Don't Override**. * To override the verbosity of runtime transaction logging for all service provider connections, select an option on the **SP Connection Transaction Logging Override** menu. The default setting is **Don't Override** * To fine-tune the caching interval for datastore validation, change the number of seconds in the **Data-Store Validation Interval** field. A value of `0` turns off the caching and validation tests are executed with each access. The default value is `300` seconds (five minutes). This setting applies to all datastores. | | | | - | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | | As you configure components on the administrative console, PingFederate performs connectivity tests against the applicable datastores. By default, PingFederate saves successful test results for five minutes. This design improves the performance of the administrative console by reducing the number of calls it makes to the target servers and the amount of time it takes to move from one configuration window to another. | * To let PingFederate use the value of a specific request header for the request ID instead of generating a request ID, enter the name of the request header in the **Request Header for Correlation ID** field. By default, the field is empty. | | | | - | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | | When a PingFederate endpoint receives HTTP requests, it records request IDs at the DEBUG level of the server log. When the **Request Header for Correlation ID** field specifies a request header, if a PingFederate endpoint receives a request that includes that header, and if the header's value contains 1 to 50 alphanumeric characters and hyphens, then PingFederate uses that value for the request ID. Otherwise, PingFederate uses a unique value that it generates for the request ID.If the request causes PingFederate to send an LDAP call to PingDirectory, PingFederate includes the request ID in the LDAP call. For auditing and troubleshooting, you can correlate the request ID in the PingFederate log with the request ID in the PingDirectory log. Learn more in [Correlating PingFederate events with PingDirectory LDAP activities](pf_correlat_pf_events_pd_ldap_activities.html). | 3. Click **Save**.