- 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.
12-18-2024 02:15 AM
this article explains how to replace the selfsigned certificate on the vault with a CA-signed cert: Article Detail
however, as we are not using TLS to connect to the vault (yet), I have the discussion with some collegues on the value of replacing the selfsigned certificate with a CA-signed certificate.
the documentation from cyberark in this case is not explicit enough to draw conclusions. I hope the community can provide details on this.
12-20-2024 08:04 AM
@Arie Hoogendoorn
Other than Prevention of Warnings ..
1) Trustworthiness: A CA-signed certificate establishes trust between the Vult nd other sytems by ensuring the identity of the Vault is verified by a trusted authority. this can be useful if your organization security policies or auditors require the use of CA-signed certificates.
2) Compliance: Many organizations have compliance requirements to use certificates issued by trusted authorities rather than self-signed ones, even if TLS is not actively being used.
I think The Vault will continue to run if the CA-signed certificate expires, but not sure 100% about that. Haven't tested .
12-20-2024 08:04 AM
@Arie Hoogendoorn
Other than Prevention of Warnings ..
1) Trustworthiness: A CA-signed certificate establishes trust between the Vult nd other sytems by ensuring the identity of the Vault is verified by a trusted authority. this can be useful if your organization security policies or auditors require the use of CA-signed certificates.
2) Compliance: Many organizations have compliance requirements to use certificates issued by trusted authorities rather than self-signed ones, even if TLS is not actively being used.
I think The Vault will continue to run if the CA-signed certificate expires, but not sure 100% about that. Haven't tested .
12-20-2024 08:42 AM
QQ:- Whatever CA signed certificate we install in vault should be installed in Component Servers too?
12-29-2024 04:28 AM
Hi @Arie Hoogendoorn
It seems that AsankaW provided an answer to your question. Could you kindly let us know if this solution helped?
If so, please mark the answer as 'Select as Best' to assist other community members.
Thank you, Liad
01-05-2025 11:22 PM
thanks @Asanka Weerasinghe ,
if talking about "trustwothiness" I also expect that components will report untrusted/expired certificates. But as we are still using CASOS to communicate (and not TLS), I do not see the security added value to have an CA-signed certificate on the vault.....from that perspective it would only be a compliance reason without security increase (and I hate compliance rules for security measures that do not add security 😉 )
nevertheless, I now have the perfect opportunity to wait for my acceptance environment which has certificates expiring within a week and see what happens.
02-03-2025 01:17 AM
Finaly we got to actively check on the behaviour when the certificate expires.
so based on above there is actually a requirement to have the certiciate not expired.
05-30-2025 05:01 AM
Even though TLS isn't currently used, replacing the self-signed certificate with a CA-signed one helps eliminate browser/security warnings and prepares the system for future secure configurations. We tested this ourselves—when the CA certificate expired, PAClient stopped working, even though Vault, PVWA, and CPM continued running. So yes, make sure your CA certificate is valid to avoid issues with PAClient functionality.
I hope it helps!
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!

