I'm facing a problem implementing a "3rd-party" digital certificate Conjur self-hosted 13.7

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

I'm facing a problem implementing a "3rd-party" digital certificate Conjur self-hosted 13.7

L1 Bithead

I'm facing a problem implementing a "3rd-party" digital certificate.

 

Domain: xpto.com

 

I installed the Conjur Self-Hosted (enterprise) cluster, version 13.7. It consists of:

 

- Cluster:

 

1 VM - leader

DNS: srvcjurleader.xpto.com

2 VMs - standby

DNS: srvcjurstandby01.xpto.com

DNS: srvcjurstandby02.xpto.com

 

2 VMs - follower

DNS: srvcjurfollower01.xpto.com

DNS: srvcjurfollower02.xpto.com

 

I have a wildcard digital certificate (*.xpto.com) that would serve all DNS servers. To configure the leader and the two standby VMs, I needed to break this certificate into several parts. I managed to generate the seeds for the two standby VMs. But when it came time to configure the two followers, I managed to import the same certificate, but when generating the follower seeds, I received the following response:

"

cyberark@srvcjurleader:~$ sudo docker exec conjur-leader evoke seed follower srvcjurfollower01.xpto.com flw-conjur.xpto.com > /tmp/seed-srvcjurfollower01.tgz

I, [2025-11-11T18:38:24.927498 #473] INFO -- : Unable to find existing certificate file 'srvcjurfollower01.xpto.com' with names: srvcjurfollower01.xpto.com, flw-conjur.xpto.com, conjur, localhost

 

An existing certificate for 'srvcjurfollower01.xpto.com' may be imported with 'evoke ca import <cert-file>'

"

I, [2025-11-11T18:38:24.927568 #473] INFO -- : Attempting to issue certificate for 'srvcjurfollower01.xpto.com'...

error: Unable to issue new certificate for 'srvcjurfollower01.xpto.com': Private key not available for CA certificate 'CN = xptoRootCA2025'

 

If Conjur should be able to issue certificates using this certificate authority, import the private key with 'evoke ca --root --key <ca-key-file> <ca-cert-file>'

 

cyberark@srvcjurleader:~$

 

From what I saw in the documentation, the leader, the standby, and the load balancer of the cluster share the same certificate.

 

The followers, however, share the certificate of the followers and the load balancer of the followers.

 

My question is... would this certificate be the one generated by the seed or the third-party certificate I want to import?

 

For the third-party certificate, do I need two certificates

1 accepted solution

Accepted Solutions

L3 Networker

For my environment, I have five Followers, but the certificate is issued only for the Load Balancer in front of them. Because of that, the certificate includes only the Load Balancer’s DNS address.

So, when I need to generate the seed file, I simply use the Load Balancer DNS in the command:

 

docker exec <leader-container-name> evoke seed follower <follower-loadbalancer-dns> > /tmp/<seed-file-name>.tar

 

I can try to help you, ping me on teams [email protected]

View solution in original post

6 REPLIES 6

L4 Transporter

Hi @Jonas Ribas​ 

 

If you have a dedicated certificate for Followers, including their own load balancer, then you need to import this certificate to the leader and standby nodes. Once this is done, check its existence in your /cert directory, and then try to seed the Followers again

 

Here is the link to the documentation part covering this process

https://docs.cyberark.com/secrets-manager-sh/latest/en/content/operations/services/cjr-rotation-certificates.html

L1 Bithead

Hi ovoloschuk (CyberArk).

 

Yes, I have a certificate for each:

 

  • Cluster certificate (leader, 02 standby, load balancer cluster)
  • Follower certificates (02 followers and load balancer followers)

Note: But I ran a test using one certificate for all DNS servers (leader, standbys, followers, and LBs) and the same problem occurs.

 

After running the evoke configure on the leader, I successfully imported the certificates into the leader.

I managed to generate the seeds for the standby groups, but when it came time to generate the seeds for the followers, I received the error again...

 

cyberark@srvcjurleader:~$ sudo docker exec conjur-leader evoke seed standby srvcjurstandby01.xpto.com srvcjurleader.xpto.com > /tmp/seed_srvcjurstandby01.tgz

[sudo] password for cyberark:

cyberark@srvcjurleader:~$ sudo docker exec conjur-leader evoke seed standby srvcjurstandby02.xpto.com srvcjurleader.xpto.com > /tmp/seed_srvcjurstandby02.tgz

NOTICE: role "clusterconjur.xpto.com" is already a member of role "standby"

cyberark@srvcjurleader:~$ sudo docker exec conjur-leader evoke seed follower srvcjurfollower01.xpto.com flw-conjur.xpto.com > /tmp/seed_srvcjurfollower01.tgz

I, [2025-11-13T19:27:50.702609 #3827] INFO -- : Unable to find existing certificate file 'srvcjurfollower01.xpto.com' with names: srvcjurfollower01.xpto.com, flw-conjur.xpto.com, conjur, localhost

 

An existing certificate for 'srvcjurfollower01.xpto.com' may be imported with 'evoke ca import <cert-file>'

 

I, [2025-11-13T19:27:50.702957 #3827] INFO -- : Attempting to issue certificate for 'srvcjurfollower01.xpto.com'...

error: Unable to issue new certificate for 'srvcjurfollower01.xpto.com': Private key not available for CA certificate 'DC = com, DC = xpto, CN = xptoIssuingCA2025'

 

If Conjur should be able to issue certificates using this certificate authority, import the private key with 'evoke ca --root --key <ca-key-file> <ca-cert-file>'

cyberark@srvcjurleader:~$ sudo docker exec conjur-leader ls -lha /opt/conjur/etc/ssl/

total 32K

drwxr-xr-x 1 root ssl-cert 4.0K Nov 13 19:11 .

drwxr-xr-x 1 conjur root 104 Nov 13 18:28 ..

lrwxrwxrwx 1 root root 6 Nov 13 19:08 5602cf14.0 -> ca.pem

-rw-r--r-- 1 root root 4.0K Nov 13 19:08 ca.pem

-rw-r----- 1 root ssl-cert 3.2K Nov 13 19:11 clusterconjur.xpto.com.key

-rw-r--r-- 1 root root 6.8K Nov 13 19:11 clusterconjur.xpto.com.pem

lrwxrwxrwx 1 root root 49 Nov 13 19:11 conjur.key -> /opt/conjur/etc/ssl/clusterconjur.xpto.com.key

lrwxrwxrwx 1 root root 49 Nov 13 19:11 conjur.pem -> /opt/conjur/etc/ssl/clusterconjur.xpto.com.pem

-rw-r----- 1 root ssl-cert 3.2K Nov 13 19:11 flw-conjur.xpto.com.key

-rw-r--r-- 1 root root 6.8K Nov 13 19:11 flw-conjur.xpto.com.pem

lrwxrwxrwx 1 root root 26 Nov 13 19:08 master.pem -> /opt/conjur/etc/ssl/ca.pem

cyberark@srvcjurleader:~$

Hi @Jonas Ribas​ 

 

Try to separate both those certs into two ones

- Cluster certificate (leader, 02 standby, load balancer cluster)

- Follower certificates (02 followers and load balancer followers)

 

For the Followers one, try to reissue your follower cert by selecting

 

Subject Name:

flw-conjur.xpto.com

 

SAN:

flw-conjur.xpto.com

srvcjurfollower01.xpto.com

srvcjurfollower02.xpto.com

 

You can then run 'openssl -text -noout in certfile.pem' to see the SANs, x509v3 extended attributes, etc. Check this on both your certs

 

Once verified > make sure the files are copied to the container either via a volume mount or using 'docker/podman cp' > reimport them to the leader node by using the commands from the previously shared docs > try to reseed the nodes again

L3 Networker

For my environment, I have five Followers, but the certificate is issued only for the Load Balancer in front of them. Because of that, the certificate includes only the Load Balancer’s DNS address.

So, when I need to generate the seed file, I simply use the Load Balancer DNS in the command:

 

docker exec <leader-container-name> evoke seed follower <follower-loadbalancer-dns> > /tmp/<seed-file-name>.tar

 

I can try to help you, ping me on teams [email protected]

L4 Transporter

Hi @Jonas Ribas​ 

 

Since several community members answered your question, could you kindly share if any of these solutions resolved your issue?

If so, could you please mark the appropriate answer as "Select as Best" to assist other community members.

 

If the issue is still relevant, I would advise raising a ticket with our support team for further assistance.

 

Thank you,

Omri

L1 Bithead

Hi guys!!!

 

Leonardo's solution also worked for me, simply passing the load balancer's DNS to the followers in the `evoke seed follower` command. This is because my followers' certificates support all the DNS servers on the machines and load balancers.

 

Thank you everyone.

  • 1 accepted solution
  • 31 Views
  • 6 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

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!