Configuring Central Credential Provider (CCP) Integration with Certificate Manager SaaS with Client Certificate Authentication

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

Configuring Central Credential Provider (CCP) Integration with Certificate Manager SaaS with Client Certificate Authentication

L1 Bithead

BLUF/tldr: Turn on Disable TLS 1.3 over TCP on your https site binding configurations if you want to use client certificate authentication from CertMgr > CCP.

 

This isn't a question, but rather I'm trying to help anyone else who's trying to integrate the Central Credential Provider with Certificate Manager SaaS and wants to use the optional client certificate authentication. I have been stuck at step 2 on the integration docs (Configure CyberArk Connection - Machine Identity Security Docs) for the past 2 weeks. When I would test the connection on the CertMgr web portal, I'd get an error similar to below:

configuration validation failed: failed to check existence of CyberArk server: read tcp <vsatellite kubernetes IP>:<port> -> <CCP IP>:443: read: connection reset by peer

When I tested without the certificate pfx archive (and after turning off all of the client cert auth settings) the test would work just fine. I confirmed that I could do client certificate authentication to the CCP from every machine I tested other than the vsatellite Kubernetes container, as I believe it's a distroless install with no useable shell. All I could see was 403.7 Forbidden: Client certificate required errors on the IIS CCP side, but I was using the same exact .pfx that I was uploading to CertMgr on my test machine successfully. I could see the vSatellite sending the communication to the CCP in the kubectl logs, but nothing really of note.

 

I eventually caved and captured a PCAP of a few failures on the CCP side and could see right before the TCP RST in the stream that it looked like there was TLS 1.3 traffic asking to downgrade to TLS 1.2. I knew from the wonderful video by Brad McDowell/cybrad (#22 - CyberArk Central Credential Provider (CCP) - YouTube) that there was an option to turn off TLS 1.3. Sure enough, after selecting the Disable TLS 1.3 over TCP option on the https site binding on the CCP server, the integration with client certificate authentication worked immediately.

 

I really thing CyberArk/Idira/Palo should definitely note something on the integration docs (Configure CyberArk Connection - Machine Identity Security Docs) somewhere in step 2 that TLS 1.3 does not work with client certificate authentication. I presume that this is probably a bug, potentially even on the Microsoft IIS side, but at least with CCP version 15.2 and vSatellite version 2.0.31 using go-resty/2.16.5, client certificate authentication does not work over TLS 1.3.

1 accepted solution

Accepted Solutions

5 REPLIES 5

L5 Sessionator

You do not need to add the any Certificate in the CCP server. You just need to add Root, and Intermediate certs in SAAS hosted servers. You just need to populate serial number in Application Tab authentication and it will work. If I have not understood your issue then just explain in simple terms here. I will try my best to fix together.

Hello Sanzu,

 

I don't actually have any issues, the integration is now working, I just wanted to document this here in case anyone else is running into the same problem I did. I'm using my company's internal PKI, so I did indeed have to add my Root certificate to the vSatellite's truststore (and just to play it safe, I also added the Issuing intermediary cert when troubleshooting, but I could remove it). The Kubernetes services on the vSatellite do appear to inherit the host machine's certificate trusts, so from a certificate trust perspective between the vSatellites and the Central Credential Provider, I think I'm all good.

 

My concern is that I had to turn of TLS 1.3 on the Central Credential Provider IIS server to get it working, while I don't think I should've had to. To be completely fair, this could be a bug with the Go based rest client that the vSatellite is using or a bug with Microsoft's implementation of TLS 1.3, but TLS 1.3 100% supports mTLS for client certificate authentications and go-resty does appear to be able to use TLS 1.3 from the packet capture I had.

 

I've reached out to my account rep to see if there's anything I'm missing here, as I don't see anything in the known issues list that say anything about the CertMgr > CCP communications needing to use TLS 1.2.

Please read this article and please let us know here what they (CA Support) say as why it is not supported.

CCP - Client Certificate Authentication Fails to Negotiate TLS/SSL Connection on Windows Server 2022...

 

 

This too.

Vault - Is TLS 1.3 officially supported by CyberArk?

I have no idea how I didn't find that when I was searching through the community last week, but that's 100% it. I might now instead suggest that they provide that link on the CertMgr SaaS integration docs in the troubleshooting section that already exists but thank you for the super quick find there!

Make friendship with @Matt Jennison​ . He helps to find article quickly.😀 Anyway you are welcome. You can still ask Idira support team as with solid reason as "Why not latest TLS in support?"

  • 1 accepted solution
  • 89 Views
  • 5 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!