ASE to ABS connectivity
To connect the API Security Enforcer (ASE) to API Behavioral Security (ABS), configure the ABS address (IPv4:<port> or <hostname>:<port>), access key, and secret key in the abs.conf
file located in the /<ASE installattion path>/pingidentity/ase/config
directory.
The |
The following table includes the parameter values and descriptions.
Parameter | Description | ||
---|---|---|---|
|
The ABS deployment mode. Valid values are |
||
|
This parameter is used when ABS is deployed in For more information on PingOne connections, see Connections. |
||
|
Use this parameter to assign an endpoint other than the one decoded by the gateway credentials. It’s used when ABS is deployed in |
||
|
The parameter has two possible configurations:
|
||
|
The access key or the username for the ABS nodes. It is the same for all the ABS nodes. The same value has to be configured in ABS MongoDB database. This value is obfuscated during the start of ASE. This parameter is used when ABS is deployed in
|
||
|
The secret key or the password for the ABS nodes. It is the same for all the ABS nodes. The same value has to be configured in ABS MongoDB database. This value is obfuscated during the start of ASE. This parameter is used when ABS is deployed in
|
||
|
Set the value to true for SSL communication between ASE and ABS. The default value is |
||
|
Location of the trusted certificate authority (CA) certificates for SSL/TLS connections from ASE to ABS. If the path parameter value is left empty, then ASE does not verify the validity of CA certificates. However, the connection to ABS is still encrypted. This parameter is used when ABS is deployed in |
The access_key
and secret_key
are configured in ABS. For more information, see ABS Admin Guide.
The following is a sample abs.conf
file:
; API Security Enforcer ABS configuration.; This file is in the standard .ini format. The comments start with a semicolon (;).; Following configurations are applicable only if ABS is enabled with true. ; Configure ABS deployment type. Supported values (onprem/cloud) deployment_type=onprem ; PingIntelligence Gateway Credentials gateway_credential= ; ABS endpoint for cloud abs_cloud_endpoint= ; a comma-separated list of abs nodes having hostname:port or ipv4:port as an address. abs_endpoint=127.0.0.1:8080 ; access key for abs node access_key=OBF:AES://ENOzsqOEhDBWLDY+pIoQ:jN6wfLiHTTd3oVNzvtXuAaOG34c4JBD4XZHgFCaHry0 ; secret key for abs node secret_key=OBF:AES:Y2DadCU4JFZp3bx8EhnOiw:zzi77GIFF5xkQJccjIrIVWU+RY5CxUhp3NLcNBel+3Q ; Setting this value to true will enable encrypted communication with ABS. enable_ssl=true ; Configure the location of ABS's trusted CA certificates. If empty, ABS's certificate ; will not be verified abs_ca_cert_path=
Configuring ASE to ABS encrypted communication
Steps
-
To enable SSL communication between ASE and ABS so that the access logs are encrypted and sent to ABS, set the value of
enable_ssl
totrue
.The
abs_ca_cert_path
is the location of ABS AI engine’s trusted CA certificate.If the field is left empty, ASE does not verify ABS AI engine’s certificate, but the communication is still encrypted.
-
Check and open ABS ports.
The default port for connection with ABS is
8080
.-
To determine ABS accessibility, run the
check_ports.sh
script on the ASE machine.Example:
/opt/pingidentity/ase/util ./check_ports.sh {ABS IPv4:[port]}
-
Input ABS host IP address and ports as arguments.
-