PingOne

Starting the gateway instance in a Docker container

About this task

Use the Docker command that you copied from PingOne to start a Docker container. Run the Docker container on a computer that can reach your Remote Authentication Dial-In User Service (RADIUS) client and PingOne.

Steps

  1. Ensure that Docker is installed and that the Docker Engine is running.

  2. Locate the Docker command that you copied earlier.

    Learn more in Adding a RADIUS gateway.

  3. Review the end user license agreement at www.pingidentity.com/en/legal/subscription-agreement.html.

  4. If you agree to the terms of the license agreement, open the Docker command in a text editor and change -e PING_IDENTITY_ACCEPT_EULA=no to -e PING_IDENTITY_ACCEPT_EULA=yes.

  5. At a command prompt, run the Docker command.

  6. (Optional) To configure a RADIUS gateway client application to use a forward web proxy server to handle traffic between the gateway and PingOne, in the run.properties file provide the relevant access information:

    • -e http_proxyHost=<HTTP_PROXY_HOST>

    • -e http_proxyPort=<HTTP_PROXY_PORT>

    • -e http_proxyUser=<HTTP_PROXY_USER>

    • -e http_proxyPassword=<HTTP_PROXY_PASSWORD>

    • -e http_proxyAuthenticationMethod=DIGEST (or BASIC)

      http_proxyHost and http_proxyPort are required to use a web proxy.

      http_proxyUser, http_proxyPassword, and http_proxyAuthenticationMethod are required if the web proxy requires authentication. a

      For http_proxyAuthenticationMethod, note that BASIC (as in basic authentication) transmits access credentials without encryption. You should therefore use DIGEST (digest authentication) because it uses a challenge-response mechanism and does not send the password in plain text.

    • You must configure the web proxy settings locally for each running instance. For example, if you are running two gateway client applications, you must configure web proxy settings for each instance separately.

    • For basic authentication to support international characters, the proxy server must also be configured to support international characters.

    • Digest authentication does not support the use of international characters.

Next steps

Verify a gateway instance