Sometimes you come across a message in the PingFederate server.log that is not generated by PingFederate itself. That message could be relayed from another piece of software. Or, PingFederate is complaining about an incompatible set up.

The distinction is important because the message can direct us to the problem. Often the problem can be resolved by resetting configuration options for the software that produced the message and passed it to PingFederate.

The following Knowledge Base articles are examples:

• LDAP: error code 3 - Timelimit Exceeded
• "Assertion audience condition validation failed" when SiteMinder sends multiple AudienceRestriction elements
• SFDC provisioner error LICENSE_LIMIT_EXCEEDED
• Apache 2.2 Reverse Proxy Rewrite Rule Not Proxying Requests to Correct PingFederate URLs