---
title: Configuring the ASE cluster SSL
description: API Security Enforcer (ASE) supports Secure Sockets Layer (SSL) over TCP for securing communications between nodes in a cluster. It uses TLS 1.2 to encrypt the communications. You can view cluster information in the controller.log file available in the /<pi_install path>/pingidentity/ase/logs/ directory.
component: pingintelligence
version: 5.2
page_id: pingintelligence:pingintelligence_reference_guide:pingintelligence_configuring_ase_cluster_ssl
canonical_url: https://docs.pingidentity.com/pingintelligence/5.2/pingintelligence_reference_guide/pingintelligence_configuring_ase_cluster_ssl.html
revdate: May 6, 2024
section_ids:
  about-this-task: About this task
  steps: Steps
---

# Configuring the ASE cluster SSL

API Security Enforcer (ASE) supports Secure Sockets Layer (SSL) *(tooltip: \<div class="paragraph">
\<p>A protocol for authenticated and encrypted links between networked machines, typically over HTTPS. SSL was deprecated in 1999 in favor of Transport Layer Security (TLS).\</p>
\</div>)* over TCP for securing communications between nodes in a cluster. It uses TLS 1.2 to encrypt the communications. You can view cluster information in the `controller.log` file available in the `/<pi_install path>/pingidentity/ase/logs/` directory.

## About this task

Configure SSL in ASE using one of the following three methods:

## Steps

1. [Using the default certificate](pingintelligence_using_the_default_certificate.html)

2. [Securing an ASE cluster](pingintelligence_securing_ase_cluster.html)

3. [Importing an existing certificate and key pair](pingintelligence_importing_existing_certificate_keypair.html)