<?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>topic Re: PVWA Load Balancing - URL in PAM Self-Hosted Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/pvwa-load-balancing-url/m-p/1297144#M1303</link>
    <description>&lt;UL&gt;&lt;LI&gt;Create a certificate for the load balanced&amp;nbsp;&lt;A alt="https://pvwa.acme.com/" href="https://pvwa.acme.com/" target="_blank"&gt;pvwa.acme.com&lt;/A&gt;&amp;nbsp;VIP/DNS. This certificate doesn't need to contain (in the SAN part for example) any reference to the individual pvwa dns hostnames isn't it ? &lt;UL&gt;&lt;LI&gt;If the Load balancer is set to offload the ssl cert, then, its not required.&lt;/LI&gt;&lt;LI&gt;If the load balancer is not set to offload the ssl cert, then new cert should have the SAN for LB url (with short name as pvwa &amp;amp; FQDN as pvwa.acme.com ), LB IPs, Individual PVWAs (hostnames &amp;amp; FQDN) &amp;amp; PVWA IPs. Then import this cert to each PVWAs.&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Sat, 30 Apr 2022 23:44:43 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2022-04-30T23:44:43Z</dc:date>
    <item>
      <title>PVWA Load Balancing - URL</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/pvwa-load-balancing-url/m-p/1297143#M1302</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I've configured two PVWA's each with their own URL, non load balanced for now, CyberArk authentication only for now:&lt;/P&gt;&lt;P&gt;https://pvwa01.acme.com/PasswordVault &lt;/P&gt;&lt;P&gt;https://pvwa02.acme.com/PasswordVault&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;CA signed ssl certificate for pvwa01.acme.com installed on that server and specified in https 443 binding of pvwa01's Default Web Site in IIS.&lt;/P&gt;&lt;P&gt;CA signed ssl certificate for pvwa02.acme.com installed on that server and specified in https 443 binding of pvwa02's Default Web Site in IIS.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;ApplicationRoot parameter in PVWA shows https://pvwa0102.acme.com/PasswordVault, https://pvwa0101.acme.com/PasswordVault&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Everything is working fine.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Now I want to load balance these PVWA's. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What actions are required at CyberArk PVWA end ? &lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Is it only a matter of pre-pending the load-balanced URL, https://pvwa.acme.com/PasswordVault, to the Application Root ?&lt;/LI&gt;&lt;LI&gt;Should I also replace the certificates on the IIS level, or can they remain as is ?&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For/At the load balancer level i guess the only actions are: &lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Create a certificate for the load balanced pvwa.acme.com VIP/DNS. This certificate doesn't need to contain (in the SAN part for example) any reference to the individual pvwa dns hostnames isn't it ?&lt;/LI&gt;&lt;LI&gt;Create the entry for the https://pvwa.acme.com/PasswordVault DNS/VIP.&lt;/LI&gt;&lt;LI&gt;Import the CA that signed the pvwa01.acme.com and pvwa02.acme.com certificates.&lt;/LI&gt;&lt;LI&gt;Create the necessary entries to load balance requests for https://pvwa.acme.com/PasswordVault (VIP/DNS) to https://pvwa01.acme.com/PasswordVault or https://pvwa02.acme.com/PasswordVault in eg round robin mode.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is the above correct, or am I missing something ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Kr&lt;/P&gt;</description>
      <pubDate>Sat, 30 Apr 2022 12:55:52 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/pvwa-load-balancing-url/m-p/1297143#M1302</guid>
      <dc:creator>edhon</dc:creator>
      <dc:date>2022-04-30T12:55:52Z</dc:date>
    </item>
    <item>
      <title>Re: PVWA Load Balancing - URL</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/pvwa-load-balancing-url/m-p/1297144#M1303</link>
      <description>&lt;UL&gt;&lt;LI&gt;Create a certificate for the load balanced&amp;nbsp;&lt;A alt="https://pvwa.acme.com/" href="https://pvwa.acme.com/" target="_blank"&gt;pvwa.acme.com&lt;/A&gt;&amp;nbsp;VIP/DNS. This certificate doesn't need to contain (in the SAN part for example) any reference to the individual pvwa dns hostnames isn't it ? &lt;UL&gt;&lt;LI&gt;If the Load balancer is set to offload the ssl cert, then, its not required.&lt;/LI&gt;&lt;LI&gt;If the load balancer is not set to offload the ssl cert, then new cert should have the SAN for LB url (with short name as pvwa &amp;amp; FQDN as pvwa.acme.com ), LB IPs, Individual PVWAs (hostnames &amp;amp; FQDN) &amp;amp; PVWA IPs. Then import this cert to each PVWAs.&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 30 Apr 2022 23:44:43 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/pvwa-load-balancing-url/m-p/1297144#M1303</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2022-04-30T23:44:43Z</dc:date>
    </item>
  </channel>
</rss>

