Configuring administrative nodes - PingAccess - 7.3

PingAccess
bundle
pingaccess-73
ft:publication_title
PingAccess
Product_Version_ce
PingAccess 7.3 (Latest)
category
Product
pa-73
pingaccess
ContentType_ce

Configure one PingAccess node as the administrative node.

Warning:

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 APIapplication programming interface (API) A specification of interactions available for building software to access an application or service..

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 in the Clustering in PingAccess reference guide.

  1. Click Settings and 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.

    1. Click + 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.

    1. Click + 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.
    Note:

    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.

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 and the Token provider section.