Page created: 12 May 2021 |
Page updated: 1 Nov 2021
Confirm that the following prerequisites are met before deploying the PingIntelligence integration.
- CA API Gateway Policy Manager - PingIntelligence was developed with and qualified with CA API Gateway 9.4 (contact PingIdentity for other supported releases). Use the included Policy Manager to configure the gateway..
PingIntelligence software installation
PingIntelligence 4.0 software is installed and configured. For installation of PingIntelligence software, refer to the manual or automated deployment guides.
- Java must be installed on the system from where the bundle is imported into the CA API gateway
Verify that ASE is in sideband mode Confirm that ASE is operating in
sidebandmode by running the following command in the ASE command line:
If ASE is not in
/opt/pingidentity/ase/bin/cli.sh status API Security Enforcer status : started mode : sideband http/ws : port 80 https/wss : port 443 firewall : enabled abs : enabled, ssl: enabled abs attack : disabled audit : enabled sideband authentication : disabled ase detected attack : disabled attack list memory : configured 128.00 MB, used 25.60 MB, free 102.40 MB
sidebandmode, then stop ASE and change the mode by editing the
sidebandand start ASE.
Enable sideband authentication: For a secure communication between CA and
ASE, enable sideband authentication by entering the following command in the ASE
# ./bin/cli.sh enable_sideband_authentication -u admin –p
Generate sideband authentication token
A token is required for CA to authenticate with ASE. This token is generated in ASE and configured in the policy XML file. To generate the token in ASE, enter the following command in the ASE command line:Save the generated authentication token for further use.
# ./bin/cli.sh -u admin -p admin create_sideband_token