Configuring load balancer as a transparent proxy to fetch credential from CCP

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

Secrets Management Articles
3 min read
L1 Bithead
No ratings

Load Balancer is a proxy server. It can operate on the HTTP, SSL, or TCP protocol communication layer.

Customers need to configure the Load Balancer so that it not only supports the SSL channel but also allows authentication using a client certificate on the CCP side. 

It is important to understand how SSL/HTTP communication works between the client and the server. First, the server tries to establish an SSL channel with the client. Authentication via the server certificate and optional authorization via the client certificate begins at this stage. The client requests the server's certificate, which is then sent, and the server optionally requests a certificate from the client. If the certificates are accepted on both sides, communication via the HTTP protocol begins.
By default, the HTTP protocol has no certificate information and was not designed for this purpose.

ka3Ht0000009YAsIAM__eid=ka3Ht0000009YAs&feoid=00N2J000009R3kl&refid=0EMHt000006kFt7.png
 

When a Load Balancer mediates between the IIS-CCP server and the client, certificate information may be lost. When the Load Balancer operates at the SSL/HTTP protocol level, the certificate information remains on the Load Balancer.

In this document, we will explain how to transmit the client certificate number to CCP by using a transparent proxy.
This way, full SSL traffic goes through the Load Balancer and the server doesn't even know about it.

Steps

The following step-by-step instructions describe how to configure the system shown in the picture above.

These steps start with the following assumptions:

  • There is already a CCP behind a Load Balancer and the Load Balancer is configured to be used as a transparent proxy.
  • There is a validated and trusted CA certificate installed on the CCP server(s).

HAProxy installation and configuration

To test this option, we used HAProxy as our Load Balancer, and we have performed the following steps to install and configure it as a transparent proxy.

  1. On the Load Balancer Machine, install HAProxy:

    > sudo apt-get update
    > sudo apt-get install haproxy

  2. Configure HAProxy as a transparent proxy. Below is an example of HAProxy configuration.

    /etc/haproxy/haproxy.cfg

    global
    (...)
      
    defaults
    (...)
      
    frontend ssl_frontend
        bind *:443
        mode tcp
        default_backend ssl_backends
      
    backend ssl_backends
        mode tcp
        balance roundrobin
        server server1 <CCP address>:443 check 

  3. Configure the client machine to direct queries to HAProxy instead of the CCP.

Traffic can now be directed to the Load Balancer, which will automatically redirect the connection to the main CCP server.

Fetch password using CCP

Send a REST query to the Load Balancer.

Use an existing application that has permission for this account:

https://<LoadBalancer IP>/aimwebservice/api/accounts?Query=safe={SafeID};object={AccountID}&appid={AppID}

Rate this article: