Page created: 19 Jul 2021 |
Page updated: 1 Nov 2021
This document discusses common error scenarios that you might encounter while working with on-premise ASE(API Security Enforcer) and PingOne API Intelligence. It also suggests the corrective steps for these issues.
ASE sends email alerts in the event of connectivity or authentication issues. You can verify the emails for preliminary error details.
|ASE is not starting after updating gateway credential in abs.conf file.||
Gateway credential is generated in PingOne. ASE parses gateway credentials and uses the information to connect with PingOne. Make sure the gateway credential is properly configured in the abs.conf file.
Verify the controller logs located under /<ASE installation>/pingidentity/ase/logs/ directory.
If the errors indicate incorrect gateway credential configuration, it is recommended to generate the gateway credentials from PingOne and reconfigure abs.conf file. For more information, see Generating a credential in PingOne.
|PingOne is not authenticating ASE consistently.||
|Experiencing constant slow log upload speeds.||ASE keeps a queue of logs to be uploaded to PingOne and uploads them on a first-come-first-serve basis. A slow upload or a blockage indicates connectivity issues. Verify your network for any disruptions. If the issue still persists, contact Ping Identity support team for resolution.|