---
title: Configuring administrative nodes
description: Configure one PingAccess node as the administrative node.
component: pingaccess
version: 9.0
page_id: pingaccess:pingaccess_user_interface_reference_guide:pa_configuring_admin_nodes
canonical_url: https://docs.pingidentity.com/pingaccess/9.0/pingaccess_user_interface_reference_guide/pa_configuring_admin_nodes.html
revdate: April 26, 2023
section_ids:
  about-this-task: About this task
  steps: Steps
  next-steps: Next steps
---

# Configuring administrative nodes

Configure one PingAccess node as the administrative node.

## About this task

|   |                                                                                                                                                            |
| - | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
|   | If you are promoting a replica administrative node to an administrative node, remove the `bootstrap.properties` file from the replica administrative node. |

In this procedure, you can specify an HTTP or HTTPS proxy. A proxy configuration defined in a properties file, such as `bootstrap.properties` or `run.properties`, takes precedence over a proxy configuration defined in the PingAccess administrative console or application programming interface (API) *(tooltip: \<div class="paragraph">
\<p>A specification of interactions available for building software to access an application or service.\</p>
\</div>)*.

If you configure a proxy on a replica administrative node and need to fail over to that node, make sure that the administrative node has the same proxy configuration as the replica administrative node before you remove the `bootstrap.properties` file from the replica administrative node.

For a comprehensive overview of the steps necessary to set up a clustered environment, see [Configuring a PingAccess cluster](../reference_guides/pa_configuring_a_pa_cluster.html) in the [Clustering in PingAccess](../reference_guides/pa_clustering_ref_guide.html) *reference guide*.

## Steps

1. Click **Settings**, then go to **Clustering > Administrative Nodes**.

2. In the **Host** field, in the **Primary Administrative Node** section, enter the host and port for the administrative console.

   The default is `localhost:9000`.

3. If applicable, specify an **HTTP Proxy** for the engine.

   For more information about creating proxies, see [Adding proxies](pa_adding_proxies.html).

   1. Click **[icon: plus, set=fa]Create** to create an HTTP proxy.

4. If applicable, specify an **HTTPS Proxy** for the engine.

   For more information about creating proxies, see [Adding proxies](pa_adding_proxies.html).

   1. Click **[icon: plus, set=fa]Create** to create an HTTPS proxy.

5. **Optional:** Select the **Enable Stale Engine Timeout** check box to remove engine node entities that have not communicated with the administrative node within the timeout value.

   |   |                                                                                                                     |
   | - | ------------------------------------------------------------------------------------------------------------------- |
   |   | This option removes the engine node entity from the administrative node but does not modify the engine node itself. |

   The default timeout value is 60 minutes. You can update this value through the PingAccess administrative API.

6. Click **Save**.

## Next steps

If you specified any proxies, enable the **Use Proxy** option for any sites, token providers, and third party services that require the use of a proxy. For more information, see [Adding sites](pa_adding_sites.html) and the [Token provider](pa_token_provider.html) section.