Central Credential Provider (CCP) IP + Certificate from behind a Load Balancer! How??

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

Central Credential Provider (CCP) IP + Certificate from behind a Load Balancer! How??

L3 Networker

I am struggling with making CCP function securely behind a load balancer / WAF. I do not trust a single factor (just certificate) to authenticate a client machine to CCP -- I would prefer that I could allow CCP/IIS to see the origin IP as well as the origin certificate. However, X-F-F requires SSL termination to insert the HTTP header so that ruins the client certificate but preserves the IP. I feel like I can only ever have one OR the other!

 

Has anybody found success here? How can this service ever be exposed safely with only a single functional factor when load balanced?

1 accepted solution

Accepted Solutions

L7 Applicator

You can just pass through the traffic and it should work . But that is messy and defeats using a load balancer .

 

The next version of ccp will support the use of an X-Header added by the lb to push the certificate serial number or potentially other certificate fields .

View solution in original post

11 REPLIES 11

L7 Applicator

You can just pass through the traffic and it should work . But that is messy and defeats using a load balancer .

 

The next version of ccp will support the use of an X-Header added by the lb to push the certificate serial number or potentially other certificate fields .

So, is there currently a best practice recommendation for exposing CCP to edge networks, cloud services, or other low-trust environments? Is it truly just "only use the certificate" currently?

L4 Transporter

Hello @Tyler Sell​ 

 

Have you received an answer to your question? If so, we kindly encourage you to share it with us.

Your insights could be valuable to other community members in the future.

 

Thank you, Isar.

L4 Transporter

Any update on this ?

Does the CCP now support allowed machines in combination with client certificate authentication for load balanced CCPs ?

L7 Applicator

Yes .

V14.2 and above of cp/ccp

 

https://docs.cyberark.com/credential-providers/latest/en/content/ccp/load-balancing-the-central-credential-provider.htm#ClientCertificateAuthentication

L4 Transporter

So, to be sure.

If I have a CCP application id configured in CyberArk that requires both allowed machines and client certificate authentication (serialnumber and/or attribute based),

Then if my source application issues a CCP REST API call to my https://<load balancer CCP VIP>/AIMWebService/... load balancer endpoint,

The load balancer will load balance via HTTPS to the CCP servers behind the load balancer, 

And that HTTPS request will contain both the source application's IP and client certificate information (serialnumber and/or attributes), 

Which can then both be extracted at CCP side, 

And be used both in combination to determine whether the source application is allowed to use the application id or not,

Is that correct ?

L7 Applicator

Yes .

With the caveat that your lb must Base64 encode the whole certificate sent and attach as an x-header , must also detect the sending ip and insert as an x-header and you have to configure ccp to trust that lb and provide the x-header names if they aren't the default .

 

 

L4 Transporter

Yes, indeed, I saw that on the page your provided.

One thing isn't clear to me yet: cfr the paragraph (table) on that page mentioning ssl termination and pass-through authentication.

In order for it to work, must the load balancer then be configured for ssl termination only ?

 

L7 Applicator

If you are using pass through then the certificate should already be being forwarded .

 

All of these instructions apply where the lb terminates the connection , then starts a new one to the ccp.

So my interpretation of that table is then

  • SSL termination only:
    • Load balancer will insert the header to include the source ip and the header to include the client certificate information.
    • This integration is supported as explained in the doco.
  • SSL passthrough only:
    • Client certificate is passed through.
    • CCP side should be able to extract client certificates serialnumber/attributes ?
    • Allowed Machines authentication: will not work, because IP received on CCP side is IP of load balancer only client certificate based authentication will work. Correct ?
  • Combination of both ?
    • Is that possible for the same client-facing load balancer VIP endpoint ?

Setting Passthrough LB and there should be option for X-forward-Header option in LB side. If this things are feasible in your case then it works.

  • 1 accepted solution
  • 251 Views
  • 11 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!