PingFederate Server

General settings

The General Settings window lets you change some of the 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 check box. This checkbox is cleared by default.

    • 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 (5 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 5 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 PingFederate receives requests, it records request IDs at the DEBUG level in the server log. If the Request Header for Correlation ID field specifies a header, and the incoming request includes that header, PingFederate uses its value as the request ID.

      PingFederate only uses header values that are between 1 and 50 characters long and contain alphanumeric characters, hyphens, or forward slashes. If the header is missing, invalid, or contains disallowed characters, PingFederate generates a unique request ID instead.

      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.

  3. Save the changes.