PingAccess

Configuring engine nodes using an auto-registration file

Download a JSON Web Token (JWT) to enable a new engine node to automatically register itself at startup in PingAccess.

Before you begin

Make sure you’ve configured an administrative node and a replica administrative node.

You can find a comprehensive overview of clustered environment configuration steps in Configuring a PingAccess cluster.

Steps

  1. Configure the new PingAccess node as an engine node:

    Choose from:

    • If the engine node isn’t a container, open the <PA_HOME>/conf/run.properties file and set the pa.operational.mode property to CLUSTERED_ENGINE. Save your changes.

    • If the engine node is a container, inject the following environment variable:

      PA_RUN_PA_OPERATIONAL_MODE=CLUSTERED_ENGINE

  2. In the PingAccess admin console, click Settings, then go to Clustering > Engine Registration.

    Configure the JWT as follows:

    1. Specify either an HTTP Proxy or HTTPS Proxy for the engine.

      Click Create to set up a new proxy if necessary. Learn more in Adding proxies.

    2. Specify an Engine Trusted Certificate if a TLS-terminating network appliance, such as a load balancer, is placed between the engine nodes and administrative node.

      Select the certificate that the network appliance uses. The certificate helps establish a secure HTTP connection with the administrative node.

    3. In the Token Duration field, enter the number of seconds for which the generated JWT is valid.

    4. Click Download.

  3. Add the JWT file you created in the previous step to the engine node:

    Choose from:

    • If the engine node isn’t a container, copy the JWT file to the <PA_HOME>/conf directory.

    • If the engine node is a container, inject the JWT as an environment variable named REGISTRATION_TOKEN.

  4. Change the name of the engine node:

    Choose from:

    • If the engine node isn’t a container, open the <PA_HOME>/conf/engine-registration.properties file and update the value of the engine.admin.api.engineName property.

    • If the engine node is a container, inject the engine node name as an environment variable named ENGINE_NAME.

  5. Start the engine node.

Next steps

Enable the Use Proxy option for any sites, token providers, and third-party services that require the use of a proxy. Learn more in Adding sites and the Token provider section.