Verify PingIntelligence Installation
Verify that all the components have installed and started successfully.
Verify ASE installation
Log in to the ASE host machine and navigate to <installation-path>/pingidentity/ase/bin directory and run the status command:
/home/pi-user/pingidentity/ase/bin/cli.sh status Ping Identity Inc., API Security Enforcer status : started mode : inline http/ws : port 8090 https/wss : port 8443 firewall : enabled abs : disabled, ssl: enabled abs attack : disabled audit : enabled ase detected attack : disabled attack list memory : configured 128.00 MB, used 25.60 MB, free 102.40 MB
If the status command runs successfully, then ASE has been installed and started.
Verify ABS and MongoDB installation
Log in to the ABS EC2 instance and run the ABS Admin REST API using a REST API client like Postman. More information on installing and configuring Postman is available in the ABS Admin Guide.
The report can be accessed by calling the ABS system at the following URL:
https://<abs_ip>:<abs_port>/v5/abs/admin. Use the IP address from the hosts file.
If ABS and MongoDB has installed successfully, the Admin REST API output will display the MongoDB nodes. If the Admin API is not accessible, then ABS has not started. Following is a sample output of the Admin REST API:
{
"company": "ping identity",
"name": "api_admin",
"description": "This report contains status information on all APIs, ABS clusters, and ASE logs",
"license_info": {
"tier": "Free",
"expiry": "Sun Jan 10 00:00:00 UTC 2021",
"max_transactions_per_month": 0,
"current_month_transactions": 30,
"max_transactions_exceeded": false,
"expired": false
},
"across_api_prediction_mode": true,
"poc": true,
"api_discovery": {
"subpath_length": "1",
"status": true
},
"apis": [
{
"api_name": "atm_app_oauth",
"host_name": "",
"url": "/atm_app_oauth",
"api_type": "regular",
"creation_date": "Thu Mar 05 08:54:01 UTC 2020",
"servers": 1,
"protocol": "https",
"cookie": "JSESSIONID",
"token": false,
"training_started_at": "Fri Feb 14 06:44:06 UTC 2020",
"training_duration": "1 hour",
"prediction_mode": true,
"apikey_header": "X-API-KEY-2",
"apikey_qs": "",
"jwt": {
"username": "",
"clientid": "",
"location": ""
}
},
{
"api_name": "root_api",
"host_name": "",
"url": "/",
"api_type": "regular",
"creation_date": "Thu Mar 05 08:54:01 UTC 2020",
"servers": 1,
"protocol": "https",
"cookie": "JSESSIONID",
"token": false,
"training_started_at": "n/a",
"training_duration": "n/a",
"prediction_mode": false,
"apikey_header": "X-API-KEY-1",
"apikey_qs": "",
"jwt": {
"username": "",
"clientid": "",
"location": ""
}
}
],
"abs_cluster": {
"abs_nodes": [
{
"node_ip": "127.0.0.1",
"os": "Red Hat Enterprise Linux Server - VMware, Inc.",
"cpu": "16",
"memory": "31G",
"filesystem": "3%",
"bootup_date": "Fri Feb 28 08:13:19 UTC 2020"
},
{
"node_ip": "127.0.0.1",
"os": "Red Hat Enterprise Linux Server - VMware, Inc.",
"cpu": "16",
"memory": "31G",
"filesystem": "4%",
"bootup_date": "Tue Mar 24 06:35:47 UTC 2020"
}
],
"mongodb_nodes": [
{
"node_ip": "127.0.0.1:27017",
"status": "primary"
}
]
},
"ase_logs": [
{
"ase_node": "88968c39-b4ea-4481-a0b4-d0d651468ab5",
"last_connected": "Thu Mar 05 08:40:14 UTC 2020",
"logs": {
"start_time": "Thu Mar 05 08:40:14 UTC 2020",
"end_time": "Thu Mar 05 08:40:14 UTC 2020",
"gzip_size": "0.74KB"
}
},
{
"ase_node": "e6b82ce9-afb3-431a-8faa-66f7ce2148b9",
"last_connected": "Thu Mar 05 08:54:06 UTC 2020",
"logs": {
"start_time": "Thu Mar 05 08:54:06 UTC 2020",
"end_time": "Thu Mar 05 08:54:06 UTC 2020",
"gzip_size": "2.82KB"
}
},
{
"ase_node": "4df50c47-407a-41f9-bda6-b72dc34dadad",
"last_connected": "Fri Feb 28 07:20:03 UTC 2020",
"logs": {
"start_time": "Tue Feb 25 12:50:00 UTC 2020",
"end_time": "Fri Feb 28 07:20:03 UTC 2020",
"gzip_size": "76.01KB"
}
},
{
"ase_node": "1910051e-5bab-44e6-8816-5b5afffdd1cf",
"last_connected": "Tue Feb 18 08:10:05 UTC 2020",
"logs": {
"start_time": "Fri Feb 14 06:42:38 UTC 2020",
"end_time": "Tue Feb 18 08:10:05 UTC 2020",
"gzip_size": "2.89MB"
}
}
],
"percentage_diskusage_limit": "80%",
"scale_config": {
"scale_up": {
"cpu_threshold": "70%",
"cpu_monitor_interval": "30 minutes",
"memory_threshold": "70%",
"memory_monitor_interval": "30 minutes",
"disk_threshold": "70%",
"disk_monitor_interval": "30 minutes"
},
"scale_down": {
"cpu_threshold": "10%",
"cpu_monitor_interval": "300 minutes",
"memory_threshold": "10%",
"memory_monitor_interval": "300 minutes",
"disk_threshold": "10%",
"disk_monitor_interval": "300 minutes"
}
},
"attack_ttl": {
"ids": [
{
"id": "ip",
"ttl": 120
},
{
"id": "cookie",
"ttl": 120
},
{
"id": "access_token",
"ttl": 120
},
{
"id": "api_key",
"ttl": 240
},
{
"id": "username",
"ttl": 360
}
]
}
}Verify Dashboard Installation
To verify the Dashboard installation, enter the Dashboard IP address from the hosts file in your web browser. Log in using ping_user or admin username and the password configured in the dashboard-defaults.yml file. If the authentication mode is set to SSO, then log in using your SSO username and password.
See the ASE, ABS and Dashboard guides for configuration and administration of PingIntelligence products.