Using Docker to run a standalone administrative console
About this task
The administrative console is available as a standalone Docker image on Docker Hub. To see a docker-compose
example that deploys a PingDirectory container with a corresponding console, see the PingDirectory getting started demo.
The Ping Identity Helm charts also include support for the administrative console, which you should use when deploying the console in Kubernetes. |
Steps
-
To connect with a PingDirectory server that is deployed in Docker, run the administrative console image in a local Docker deployment.
The network you use must match the network used by the PingDirectory server’s container.
Example:
The following example deploys the standalone console image in a local Docker deployment with the console listening on port
8443
using thepingnet
network:docker run \ --name pingdataconsole \ --publish 8443:8443 \ --network pingnet \ --detach \ pingidentity/pingdataconsole:edge
You can change the first port in the
--publish
line based on what port you want to use on your local machine, but you shouldn’t change the second port. To access the console outside of Docker on port9443
, for example, use9443:8443
. -
To access the console, go to https://<hostname>:<port>/console/login and enter the following credentials.
Field Credential Server
<PingDirectory container name>:<LDAPS port>
The name of the server you enter on the sign-on page must match the name of the PingDirectory container you are trying to connect to along with the LDAPS port of that container.
For example, use
pingdirectory:1636
to connect to a standalone PingDirectory Docker container on the same network.Username
administrator
Password
2FederateM0re