- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
08-19-2024 08:05 AM
For Privilege Cloud, you may need to reach out to support to identify the specifics.
As a CyberArk employee, I was able to look at the certificate on the backend for your tenant - it is a valid certificate from an enterprise CA.
On your end, you will need to make sure that the Privilege Cloud Connector servers all have a client certificate that is signed by this CA - that is how you establish trust with the CyberArk backend.
Basically, look at the personal certificate store on your PCC servers and locate the one signed by your enterprise CA - is it expired? If so, renew the certificate, load the certificate to RDS, and trust for the HTML5 gateway should be restored.
KA for certificate work: https://community.cyberark.com/s/article/Privilege-Cloud-HTML5-Certificate-Troubleshooting
Documentation showing the RDS certificate step (easy to miss on other pages!): https://docs.cyberark.com/ispss-deployment/latest/en/Content/Privilege%20Cloud/privCloud-config-remote-access-html5gw-service.htm?tocpath=Configure%20CyberArk%20services%7CSet%20remote%20access%20to%20target%20machines%7C_____1
08-19-2024 05:53 AM
Hi,
If you have admin access on your alero tenant, go to Sites >> Applications >> PVWA:
Within your PVWA configuration, you will have an HTML5 drop down. There, you will be able to check your html5 internal url.
When you have that just do a nslookup and find out which machine is it.
Then, just follow CyberArk guidance to change the certificate
Hope this was helpfull
08-19-2024 05:53 AM
Hi,
If you have admin access on your alero tenant, go to Sites >> Applications >> PVWA:
Within your PVWA configuration, you will have an HTML5 drop down. There, you will be able to check your html5 internal url.
When you have that just do a nslookup and find out which machine is it.
Then, just follow CyberArk guidance to change the certificate
Hope this was helpfull
08-19-2024 08:05 AM
For Privilege Cloud, you may need to reach out to support to identify the specifics.
As a CyberArk employee, I was able to look at the certificate on the backend for your tenant - it is a valid certificate from an enterprise CA.
On your end, you will need to make sure that the Privilege Cloud Connector servers all have a client certificate that is signed by this CA - that is how you establish trust with the CyberArk backend.
Basically, look at the personal certificate store on your PCC servers and locate the one signed by your enterprise CA - is it expired? If so, renew the certificate, load the certificate to RDS, and trust for the HTML5 gateway should be restored.
KA for certificate work: https://community.cyberark.com/s/article/Privilege-Cloud-HTML5-Certificate-Troubleshooting
Documentation showing the RDS certificate step (easy to miss on other pages!): https://docs.cyberark.com/ispss-deployment/latest/en/Content/Privilege%20Cloud/privCloud-config-remote-access-html5gw-service.htm?tocpath=Configure%20CyberArk%20services%7CSet%20remote%20access%20to%20target%20machines%7C_____1
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!

