Part B – Install ASE - PingIntelligence for APIs

Part B – Install ASE - PingIntelligence for APIs - 5.0

PingIntelligence

bundle

pingintelligence-50

ft:publication_title

PingIntelligence

Product_Version_ce

PingIntelligence for APIs 5.0

category

APISecurity

AdvancedAPICybersecurity

Capability

Environment

Product

apisecurity

capability

linux

pi-50

pingintelligence

private

ContentType_ce

Page created: 12 May 2021 |

Page updated: 1 Nov 2021

| 1 min read

5.0 Capability API Security Advanced API Cybersecurity Linux On-Premises Operating System Hosting Environment PingIntelligence for APIs Product Installation User task

This section summarizes the key processes involved in API Enforcer Enforcer (ASE) installation.

A new ASE installation involves following steps:

Understanding and determining ASE deployment modes.
Provisioning the host system based on number of APIs and the expected queries per second (QPS). For information on sizing, contact Ping Identity support team.
Reviewing port requirements.
Installing ASE.
Copying ASE license.
Changing default settings.
Obfuscating keys and passwords.
Tuning host system for high performance.
Starting ASE.
Configure SSL for client side connection or external APIs

Note: ASE cluster setup facilitates high availability and increases both performance and overall system throughput. It is Ping Identity recommends setting up a cluster of ASE nodes for production environments. For more information on setting up an ASE cluster, see Setup ASE cluster (optional) and Administering an ASE cluster.

After installing ASE, proceed with the following tasks:

Configuring ASE - ASE system level configuration entails modifying parameters in the ase.conf file located in the config directory. For more information, see Sideband ASE configuration or Inline ASE configuration
Configuring deployment method - PingIntelligence supports on-premise and cloud deployment options. You can integrate ASE in hybrid mode with PingOne API Intelligence, which is a cloud based service. For more information, see Configure deployment method.