<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>article Configuring load balancer as a transparent proxy to fetch credential from CCP in Secrets Management Articles</title>
    <link>https://live.paloaltonetworks.com/t5/secrets-management-articles/configuring-load-balancer-as-a-transparent-proxy-to-fetch/ta-p/1428738</link>
    <description>&lt;P&gt;&lt;EM&gt;Load Balancer&lt;/EM&gt;&amp;nbsp;is a proxy server. It can operate on the&amp;nbsp;&lt;EM&gt;HTTP, SSL, or TCP&lt;/EM&gt;&amp;nbsp;protocol communication layer.&lt;/P&gt;
&lt;P&gt;Customers need to configure the Load Balancer so that it not only supports the&amp;nbsp;&lt;EM&gt;SSL&lt;/EM&gt;&amp;nbsp;channel but also allows authentication using a client certificate on the&amp;nbsp;&lt;EM&gt;CCP&lt;/EM&gt;&amp;nbsp;side.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It is important to understand how&amp;nbsp;&lt;EM&gt;SSL/HTTP&lt;/EM&gt;&amp;nbsp;communication works between the client and the server. First, the server tries to establish an&amp;nbsp;&lt;EM&gt;SSL&lt;/EM&gt;&amp;nbsp;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&amp;nbsp;&lt;INS&gt;&lt;EM&gt;HTTP&lt;/EM&gt;&amp;nbsp;protocol begins&lt;/INS&gt;.&lt;BR /&gt;By default, the&amp;nbsp;&lt;EM&gt;HTTP&lt;/EM&gt;&amp;nbsp;protocol has no certificate information and was not designed for this purpose.&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="ka3Ht0000009YAsIAM__eid=ka3Ht0000009YAs&amp;amp;feoid=00N2J000009R3kl&amp;amp;refid=0EMHt000006kFt7.png"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/98618iA1F7FD10718D89A9/image-size/large?v=v2&amp;amp;px=999" role="button" title="ka3Ht0000009YAsIAM__eid=ka3Ht0000009YAs&amp;amp;feoid=00N2J000009R3kl&amp;amp;refid=0EMHt000006kFt7.png" alt="ka3Ht0000009YAsIAM__eid=ka3Ht0000009YAs&amp;amp;feoid=00N2J000009R3kl&amp;amp;refid=0EMHt000006kFt7.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;When a Load Balancer mediates between the&amp;nbsp;&lt;EM&gt;IIS-CCP&lt;/EM&gt;&amp;nbsp;server and the client, certificate information may be lost. When the Load Balancer operates at the&amp;nbsp;&lt;EM&gt;SSL/HTTP&lt;/EM&gt;&amp;nbsp;protocol level, the certificate information remains on the Load Balancer.&lt;/P&gt;
&lt;P&gt;In this document, we will explain how to transmit the client certificate number to&amp;nbsp;&lt;EM&gt;CCP&lt;/EM&gt;&amp;nbsp;by using a&amp;nbsp;&lt;STRONG&gt;transparent proxy&lt;/STRONG&gt;.&lt;BR /&gt;This way, full&amp;nbsp;&lt;EM&gt;SSL&lt;/EM&gt;&amp;nbsp;traffic goes through the Load Balancer and the server doesn't even know about it.&lt;/P&gt;
&lt;H3&gt;Steps&lt;/H3&gt;
&lt;P&gt;The following step-by-step instructions describe how to configure the system shown in the picture above.&lt;/P&gt;
&lt;P&gt;These steps start with the following assumptions:&lt;/P&gt;
&lt;UL&gt;&lt;LI&gt;There is already a CCP behind a Load Balancer and the Load Balancer is configured to be used as a transparent proxy.&lt;/LI&gt;&lt;LI&gt;There is a validated and trusted CA certificate installed on the CCP server(s).&lt;/LI&gt;&lt;/UL&gt;
&lt;H2 id="KAConfiguringloadbalancerasatransparentproxytofetchcredentialfromCCP-HAProxyinstallationandconfiguration"&gt;&lt;STRONG&gt;HAProxy installation and configuration&lt;/STRONG&gt;&lt;/H2&gt;
&lt;P&gt;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&amp;nbsp;&lt;STRONG&gt;transparent proxy&lt;/STRONG&gt;.&lt;/P&gt;
&lt;OL&gt;&lt;LI&gt;
&lt;P&gt;On the Load Balancer Machine, install HAProxy:&lt;/P&gt;
&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD colspan="1" rowspan="1"&gt;
&lt;P&gt;&lt;CODE&gt;&amp;gt;&amp;nbsp;&lt;/CODE&gt;&lt;CODE&gt;sudo&lt;/CODE&gt;&amp;nbsp;&lt;CODE&gt;apt-get update&lt;/CODE&gt;&lt;BR /&gt; &lt;CODE&gt;&amp;gt;&amp;nbsp;&lt;/CODE&gt;&lt;CODE&gt;sudo&lt;/CODE&gt;&amp;nbsp;&lt;CODE&gt;apt-get&amp;nbsp;&lt;/CODE&gt;&lt;CODE&gt;install&lt;/CODE&gt;&amp;nbsp;&lt;CODE&gt;haproxy&lt;/CODE&gt;&lt;/P&gt;
&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;
&lt;/LI&gt;&lt;LI&gt;
&lt;P&gt;Configure&amp;nbsp;&lt;EM&gt;HAProxy&lt;/EM&gt;&amp;nbsp;as a transparent proxy. Below is an example of&amp;nbsp;&lt;EM&gt;HAProxy&amp;nbsp;&lt;/EM&gt;configuration&lt;EM&gt;.&lt;/EM&gt;&lt;BR /&gt; &lt;BR /&gt; &lt;STRONG&gt;/etc/haproxy/haproxy.cfg&lt;/STRONG&gt;&lt;/P&gt;
&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD colspan="1" rowspan="1"&gt;
&lt;P&gt;&lt;CODE&gt;global&lt;/CODE&gt;&lt;BR /&gt; &lt;CODE&gt;(...)&lt;/CODE&gt;&lt;BR /&gt; &lt;CODE&gt;&amp;nbsp;&lt;/CODE&gt;&amp;nbsp;&lt;BR /&gt; &lt;CODE&gt;defaults&lt;/CODE&gt;&lt;BR /&gt; &lt;CODE&gt;(...)&lt;/CODE&gt;&lt;BR /&gt; &lt;CODE&gt;&amp;nbsp;&lt;/CODE&gt;&amp;nbsp;&lt;BR /&gt; &lt;CODE&gt;frontend ssl_frontend&lt;/CODE&gt;&lt;BR /&gt; &lt;CODE&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/CODE&gt;&lt;CODE&gt;bind *:443&lt;/CODE&gt;&lt;BR /&gt; &lt;CODE&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/CODE&gt;&lt;CODE&gt;mode tcp&lt;/CODE&gt;&lt;BR /&gt; &lt;CODE&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/CODE&gt;&lt;CODE&gt;default_backend ssl_backends&lt;/CODE&gt;&lt;BR /&gt; &lt;CODE&gt;&amp;nbsp;&lt;/CODE&gt;&amp;nbsp;&lt;BR /&gt; &lt;CODE&gt;backend ssl_backends&lt;/CODE&gt;&lt;BR /&gt; &lt;CODE&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/CODE&gt;&lt;CODE&gt;mode tcp&lt;/CODE&gt;&lt;BR /&gt; &lt;CODE&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/CODE&gt;&lt;CODE&gt;balance roundrobin&lt;/CODE&gt;&lt;BR /&gt; &lt;CODE&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/CODE&gt;&lt;CODE&gt;server server1 &amp;lt;CCP address&amp;gt;:443 check&amp;nbsp;&lt;/CODE&gt;&lt;/P&gt;
&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;
&lt;/LI&gt;&lt;LI&gt;Configure the client machine to direct queries to&amp;nbsp;&lt;EM&gt;HAProxy&lt;/EM&gt;&amp;nbsp;instead of the&amp;nbsp;&lt;EM&gt;CCP&lt;/EM&gt;.&lt;/LI&gt;&lt;/OL&gt;
&lt;P&gt;Traffic can now be directed to the Load Balancer, which will automatically redirect the connection to the main&amp;nbsp;&lt;EM&gt;CCP&lt;/EM&gt;&amp;nbsp;server.&lt;/P&gt;
&lt;H2 id="KAConfiguringloadbalancerasatransparentproxytofetchcredentialfromCCP-FetchpasswordusingCCP"&gt;&lt;STRONG&gt;Fetch password using CCP&lt;/STRONG&gt;&lt;/H2&gt;
&lt;P&gt;Send a REST query to the Load Balancer.&lt;/P&gt;
&lt;P&gt;Use an existing application that has permission for this account:&lt;/P&gt;
&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD colspan="1" rowspan="1"&gt;
&lt;P&gt;&lt;CODE&gt;https://&amp;lt;LoadBalancer IP&amp;gt;/aimwebservice/api/accounts?Query=safe={SafeID};object={AccountID}&amp;amp;appid={AppID}&lt;/CODE&gt;&lt;/P&gt;
&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;</description>
    <pubDate>Tue, 12 Mar 2024 14:53:54 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2024-03-12T14:53:54Z</dc:date>
    <item>
      <title>Configuring load balancer as a transparent proxy to fetch credential from CCP</title>
      <link>https://live.paloaltonetworks.com/t5/secrets-management-articles/configuring-load-balancer-as-a-transparent-proxy-to-fetch/ta-p/1428738</link>
      <description>&lt;P&gt;&lt;EM&gt;Load Balancer&lt;/EM&gt;&amp;nbsp;is a proxy server. It can operate on the&amp;nbsp;&lt;EM&gt;HTTP, SSL, or TCP&lt;/EM&gt;&amp;nbsp;protocol communication layer.&lt;/P&gt;
&lt;P&gt;Customers need to configure the Load Balancer so that it not only supports the&amp;nbsp;&lt;EM&gt;SSL&lt;/EM&gt;&amp;nbsp;channel but also allows authentication using a client certificate on the&amp;nbsp;&lt;EM&gt;CCP&lt;/EM&gt;&amp;nbsp;side.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It is important to understand how&amp;nbsp;&lt;EM&gt;SSL/HTTP&lt;/EM&gt;&amp;nbsp;communication works between the client and the server. First, the server tries to establish an&amp;nbsp;&lt;EM&gt;SSL&lt;/EM&gt;&amp;nbsp;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&amp;nbsp;&lt;INS&gt;&lt;EM&gt;HTTP&lt;/EM&gt;&amp;nbsp;protocol begins&lt;/INS&gt;.&lt;BR /&gt;By default, the&amp;nbsp;&lt;EM&gt;HTTP&lt;/EM&gt;&amp;nbsp;protocol has no certificate information and was not designed for this purpose.&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="ka3Ht0000009YAsIAM__eid=ka3Ht0000009YAs&amp;amp;feoid=00N2J000009R3kl&amp;amp;refid=0EMHt000006kFt7.png"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/98618iA1F7FD10718D89A9/image-size/large?v=v2&amp;amp;px=999" role="button" title="ka3Ht0000009YAsIAM__eid=ka3Ht0000009YAs&amp;amp;feoid=00N2J000009R3kl&amp;amp;refid=0EMHt000006kFt7.png" alt="ka3Ht0000009YAsIAM__eid=ka3Ht0000009YAs&amp;amp;feoid=00N2J000009R3kl&amp;amp;refid=0EMHt000006kFt7.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;When a Load Balancer mediates between the&amp;nbsp;&lt;EM&gt;IIS-CCP&lt;/EM&gt;&amp;nbsp;server and the client, certificate information may be lost. When the Load Balancer operates at the&amp;nbsp;&lt;EM&gt;SSL/HTTP&lt;/EM&gt;&amp;nbsp;protocol level, the certificate information remains on the Load Balancer.&lt;/P&gt;
&lt;P&gt;In this document, we will explain how to transmit the client certificate number to&amp;nbsp;&lt;EM&gt;CCP&lt;/EM&gt;&amp;nbsp;by using a&amp;nbsp;&lt;STRONG&gt;transparent proxy&lt;/STRONG&gt;.&lt;BR /&gt;This way, full&amp;nbsp;&lt;EM&gt;SSL&lt;/EM&gt;&amp;nbsp;traffic goes through the Load Balancer and the server doesn't even know about it.&lt;/P&gt;
&lt;H3&gt;Steps&lt;/H3&gt;
&lt;P&gt;The following step-by-step instructions describe how to configure the system shown in the picture above.&lt;/P&gt;
&lt;P&gt;These steps start with the following assumptions:&lt;/P&gt;
&lt;UL&gt;&lt;LI&gt;There is already a CCP behind a Load Balancer and the Load Balancer is configured to be used as a transparent proxy.&lt;/LI&gt;&lt;LI&gt;There is a validated and trusted CA certificate installed on the CCP server(s).&lt;/LI&gt;&lt;/UL&gt;
&lt;H2 id="KAConfiguringloadbalancerasatransparentproxytofetchcredentialfromCCP-HAProxyinstallationandconfiguration"&gt;&lt;STRONG&gt;HAProxy installation and configuration&lt;/STRONG&gt;&lt;/H2&gt;
&lt;P&gt;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&amp;nbsp;&lt;STRONG&gt;transparent proxy&lt;/STRONG&gt;.&lt;/P&gt;
&lt;OL&gt;&lt;LI&gt;
&lt;P&gt;On the Load Balancer Machine, install HAProxy:&lt;/P&gt;
&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD colspan="1" rowspan="1"&gt;
&lt;P&gt;&lt;CODE&gt;&amp;gt;&amp;nbsp;&lt;/CODE&gt;&lt;CODE&gt;sudo&lt;/CODE&gt;&amp;nbsp;&lt;CODE&gt;apt-get update&lt;/CODE&gt;&lt;BR /&gt; &lt;CODE&gt;&amp;gt;&amp;nbsp;&lt;/CODE&gt;&lt;CODE&gt;sudo&lt;/CODE&gt;&amp;nbsp;&lt;CODE&gt;apt-get&amp;nbsp;&lt;/CODE&gt;&lt;CODE&gt;install&lt;/CODE&gt;&amp;nbsp;&lt;CODE&gt;haproxy&lt;/CODE&gt;&lt;/P&gt;
&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;
&lt;/LI&gt;&lt;LI&gt;
&lt;P&gt;Configure&amp;nbsp;&lt;EM&gt;HAProxy&lt;/EM&gt;&amp;nbsp;as a transparent proxy. Below is an example of&amp;nbsp;&lt;EM&gt;HAProxy&amp;nbsp;&lt;/EM&gt;configuration&lt;EM&gt;.&lt;/EM&gt;&lt;BR /&gt; &lt;BR /&gt; &lt;STRONG&gt;/etc/haproxy/haproxy.cfg&lt;/STRONG&gt;&lt;/P&gt;
&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD colspan="1" rowspan="1"&gt;
&lt;P&gt;&lt;CODE&gt;global&lt;/CODE&gt;&lt;BR /&gt; &lt;CODE&gt;(...)&lt;/CODE&gt;&lt;BR /&gt; &lt;CODE&gt;&amp;nbsp;&lt;/CODE&gt;&amp;nbsp;&lt;BR /&gt; &lt;CODE&gt;defaults&lt;/CODE&gt;&lt;BR /&gt; &lt;CODE&gt;(...)&lt;/CODE&gt;&lt;BR /&gt; &lt;CODE&gt;&amp;nbsp;&lt;/CODE&gt;&amp;nbsp;&lt;BR /&gt; &lt;CODE&gt;frontend ssl_frontend&lt;/CODE&gt;&lt;BR /&gt; &lt;CODE&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/CODE&gt;&lt;CODE&gt;bind *:443&lt;/CODE&gt;&lt;BR /&gt; &lt;CODE&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/CODE&gt;&lt;CODE&gt;mode tcp&lt;/CODE&gt;&lt;BR /&gt; &lt;CODE&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/CODE&gt;&lt;CODE&gt;default_backend ssl_backends&lt;/CODE&gt;&lt;BR /&gt; &lt;CODE&gt;&amp;nbsp;&lt;/CODE&gt;&amp;nbsp;&lt;BR /&gt; &lt;CODE&gt;backend ssl_backends&lt;/CODE&gt;&lt;BR /&gt; &lt;CODE&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/CODE&gt;&lt;CODE&gt;mode tcp&lt;/CODE&gt;&lt;BR /&gt; &lt;CODE&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/CODE&gt;&lt;CODE&gt;balance roundrobin&lt;/CODE&gt;&lt;BR /&gt; &lt;CODE&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/CODE&gt;&lt;CODE&gt;server server1 &amp;lt;CCP address&amp;gt;:443 check&amp;nbsp;&lt;/CODE&gt;&lt;/P&gt;
&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;
&lt;/LI&gt;&lt;LI&gt;Configure the client machine to direct queries to&amp;nbsp;&lt;EM&gt;HAProxy&lt;/EM&gt;&amp;nbsp;instead of the&amp;nbsp;&lt;EM&gt;CCP&lt;/EM&gt;.&lt;/LI&gt;&lt;/OL&gt;
&lt;P&gt;Traffic can now be directed to the Load Balancer, which will automatically redirect the connection to the main&amp;nbsp;&lt;EM&gt;CCP&lt;/EM&gt;&amp;nbsp;server.&lt;/P&gt;
&lt;H2 id="KAConfiguringloadbalancerasatransparentproxytofetchcredentialfromCCP-FetchpasswordusingCCP"&gt;&lt;STRONG&gt;Fetch password using CCP&lt;/STRONG&gt;&lt;/H2&gt;
&lt;P&gt;Send a REST query to the Load Balancer.&lt;/P&gt;
&lt;P&gt;Use an existing application that has permission for this account:&lt;/P&gt;
&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD colspan="1" rowspan="1"&gt;
&lt;P&gt;&lt;CODE&gt;https://&amp;lt;LoadBalancer IP&amp;gt;/aimwebservice/api/accounts?Query=safe={SafeID};object={AccountID}&amp;amp;appid={AppID}&lt;/CODE&gt;&lt;/P&gt;
&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;</description>
      <pubDate>Tue, 12 Mar 2024 14:53:54 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/secrets-management-articles/configuring-load-balancer-as-a-transparent-proxy-to-fetch/ta-p/1428738</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2024-03-12T14:53:54Z</dc:date>
    </item>
  </channel>
</rss>

