<?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: CCP Allowed machine and Client SSL authentication in PAM Self-Hosted Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/ccp-allowed-machine-and-client-ssl-authentication/m-p/1361668#M50695</link>
    <description>&lt;P&gt;AFAIK, you can do it with LB being in Transparent proxy mode (So that it passes the real client IP). That let's you use the Certs &amp;amp; Machine IP together. &lt;/P&gt;</description>
    <pubDate>Wed, 28 Apr 2021 17:43:14 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2021-04-28T17:43:14Z</dc:date>
    <item>
      <title>CCP Allowed machine and Client SSL authentication</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/ccp-allowed-machine-and-client-ssl-authentication/m-p/1361667#M50694</link>
      <description>&lt;P&gt;Has anyone configured allowed machine in combination with client certificate for CCP?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The following KB article has detailed steps to authenticate with allowed machine, however adding X-forward header terminates the SSL at LB level and in turn prevents client certificate validation at CCP. As far I see, these options are mutually exclusive. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there a way to configure F5 to allow both Allowed machines and Client certificate authentication at CCP?&lt;/P&gt;</description>
      <pubDate>Mon, 26 Apr 2021 05:39:23 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/ccp-allowed-machine-and-client-ssl-authentication/m-p/1361667#M50694</guid>
      <dc:creator>mband</dc:creator>
      <dc:date>2021-04-26T05:39:23Z</dc:date>
    </item>
    <item>
      <title>Re: CCP Allowed machine and Client SSL authentication</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/ccp-allowed-machine-and-client-ssl-authentication/m-p/1361668#M50695</link>
      <description>&lt;P&gt;AFAIK, you can do it with LB being in Transparent proxy mode (So that it passes the real client IP). That let's you use the Certs &amp;amp; Machine IP together. &lt;/P&gt;</description>
      <pubDate>Wed, 28 Apr 2021 17:43:14 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/ccp-allowed-machine-and-client-ssl-authentication/m-p/1361668#M50695</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2021-04-28T17:43:14Z</dc:date>
    </item>
    <item>
      <title>Re: CCP Allowed machine and Client SSL authentication</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/ccp-allowed-machine-and-client-ssl-authentication/m-p/1361669#M50696</link>
      <description>&lt;P&gt;Hi , were you able to make this work using Transparent proxy mode , i am also trying the same authentication methods.  have asked my LB team to check the Transparent proxy mode.&lt;/P&gt;&lt;P&gt;Are there any links or doc on how to setup this up with Transparent proxy mode&lt;/P&gt;</description>
      <pubDate>Tue, 17 May 2022 13:45:08 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/ccp-allowed-machine-and-client-ssl-authentication/m-p/1361669#M50696</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2022-05-17T13:45:08Z</dc:date>
    </item>
  </channel>
</rss>

