PingCentral can be installed on Microsoft Windows Server 2016 or 2019. An installation script is not yet available, so download and extract the contents of the installation file to a suitable location within the host file system.
- You are signed on to your system and have privileges that allow you to install applications.
- All system requirements are met, and the Oracle Java 11 LTS runtime environment is installed.
- The <JAVA_HOME> path points to the JDK software on your system. For example, /usr/lib/jvm/java-11-openjdk-184.108.40.206-0.e17_7.x86_64. To verify this information, run the echo $JAVA_HOME command.
- The JAVA /bin directory path is added to the <PATH> variable. To verify this information, run the $echo $PATH command.
- Download the distribution .zip archive and extract its contents where you want the service run.
- Go to /<pingcentral_install>/bin/run.bat and run run.bat from a command-line interface.
Open a web browser and go to https://localhost:9022.
While you are running PingCentral locally, your browser might warn you that the application you're accessing doesn't have a signed certificate.
Sign on to PingCentral using the following
- Username: Administrator
- Password: 2Federate
Without modification, PingCentral is secure by default.Items worth mentioning:
- If you add PingAccess environments to PingCentral, ensure that PingFederate is configured as the PingAccess token provider. See Configuring PingFederate as a PingAccess token for details.
- If your application owners promote SAML applications to PingFederate or PingAccess environments, ensure that the appropriate trusted certificate authority (CA) certificates are available in PingCentral. See Adding trusted CA certificates to PingCentral for details.
Configure PingCentral to run as a Windows
service, if appropriate.
For more information, see Configuring PingCentral to run as a Windows service.