key fileĬertificate of the signing root CA, as a. Private key that matches the PSM HTML5 gateway remote certificate's public key, as a. Place the following items in the directory you created in step 1:Ĭertificate to use as the PSM HTML5 gateway certificate, as a. Use an existing PSM HTML5 gateway certificate from your organization Use an existing certificate within your organization or create a new certificate. Prepare a certificate for the PSM HTML5 gateway. On the host machine, create a directory for the certificate and related files. Run the container with an imported SSL certificate Replace with the fully qualified domain name (FQDN) of the machine. The values of the -name option and the -hostname option in this command must be identical. For more details, see Validate the PSM remote certificate, below. PSM certificate settings - Set either PSMCAFile (preferred) or IgnorePSMCertificateErrors. For more details, see Disable JWT validation, below. JWT validaton - Set EnableJWTValidation=no. When you run the HTML5 Gateway container using the docker run command, make sure you specify the following options: Sudo docker run -restart unless-stopped -ti -d -cap-drop=all -cap-add= -e AcceptCyberArkEULA=yes -e EnableJWTValidation=no -e IgnorePSMCertificateErrors=yes -hostname -name docker.io/alerocyberark/psmhtml5 Use the following command to run a PSM HTML5 gateway container instance. Run the container with an auto-created SSL certificate You can choose whether to create an SSL certificate automatically when the container starts, or to import an existing certificate. The PSM HTML5 gateway must use an SSL certificate to provide secure communication.
0 kommentar(er)
