After the installation is complete, refer to the following topics based on the type of deployment.
Sideband configuration
After you have completed the deployment, integrate one of the following API gateways with PingIntelligence components and start sending the API traffic to your API gateway:
- Akana API gateway sideband integration
- Apigee integration
- AWS API Gateway integration
- Azure APIM sideband integration
- Axway sideband integration
- CA API gateway sideband integration
- F5 BIG-IP integration
- IBM DataPower Gateway sideband integration
- Kong API gateway integration
- MuleSoft sideband integration
- NGINX sideband integration
- NGINX Plus sideband integration
- PingAccess sideband integration
- PingFederate sideband integration
- WSO2 integration
Inline configuration
If you configured PingIntelligence ASE as Inline ASE, the next step is to add Defining an API using API JSON configuration file in inline mode.
After adding API definitions, direct your API client to the IP address of the ASE software on port 80 or 443.
Refer to the following topics within the ASE and ABS Admin Guides:
After you have added your APIs in ASE, the API model needs to be trained. The training of the API model is completed in ABS.
Training the API model
After you have added your APIs in ASE, the API model needs to be trained. The training of the API model is completed in ABS. The following topics give a high-level overview of the training process; however, it is recommended to review the entire ABS Admin Guide:
- Train your API model
- Generate and view the REST API
reports using PostmanNote:
To access the ABS REST API reports, you will need the following information:
- IP address: The IP address of ABS configured in the config/hosts file.
- Port number: The default value is 8080. It is configured in the abs-defaults.yml file.
- API name: Name of the API for which you want to generate REST API reports.
- Date range: The date range for which you want to generate the reports.
- Accessing the PingIntelligence DashboardNote:
Sign on to the PingIntelligence for APIs Dashboard using the
ping_userusername and the password that you configured during PingIntelligence installation. For more information on password configuration, see Changing Dashboard default settings. The PingIntelligence Dashboard takes approximately one hour to start showing attack information.