The General Settings window lets you change some of the general system-wide settings for your PingFederate servers.
- Go to .
Change any of the following settings:
- To turn off automatic multi-connection error checking, select the Disable Automatic Connection Validation check box. This check box is not selected 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 (five
minutes). This setting applies to all datastores.Note:
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.Note:
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. For more information, see Correlating PingFederate events with PingDirectory LDAP activities.
- Save the changes.