Verifying PingIntelligence installation
Verify that all PingIntelligence components have installed and started successfully.
Verifying ASE installation
About this task
To verify ASE was successfully installed:
Steps
-
Sign on to the ASE host machine and navigate to
<installation-path>/pingidentity/ase/bindirectory. -
Run the
statuscommand:/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
Result:
If the
statuscommand runs successfully, then ASE has been installed and started.
Verifying ABS and MongoDB installation
About this task
To verify ABS and MongoDB were successfully installed:
Steps
-
Sign on to the ABS EC2 instance and run the ABS Admin REST API using a REST API client, such as Postman.
For more information on installing and configuring Postman, see ABS Administration.
-
To access the REST API report, call the ABS system at the following URL: https://<abs_ip>:<abs_port>/v5/abs/admin. Use the IP address from the
hostsfile.Result:
If ABS and MongoDB were installed successfully, the Admin REST API output will display the MongoDB nodes. If the admin API is not accessible, then ABS has not started. The 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 } ] } }
Verifying Dashboard installation
About this task
To verify Dashboard installation:
Steps
-
Enter the Dashboard IP address from the
hostsfile in your web browser. -
Sign on using
ping_useroradminas the username and the password configured in thedashboard-defaults.ymlfile. If the authentication mode is set toSSO, then sign on using your SSO username and password.
Next steps
See the API Security Enforcer, ABS AI Engine, and PingIntelligence Dashboard guides for configuration and administration of PingIntelligence products.