<?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 Password Retrieval Call in PAM Self-Hosted Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/ccp-password-retrieval-call/m-p/1302816#M6009</link>
    <description>&lt;P&gt;-Check licencing - your licence may be per host accessing CCP.&lt;/P&gt;&lt;P&gt;-Make sure ccp is properly spec'd and configured. Otherwise it will be DOS'd by that number lf connections. &lt;/P&gt;&lt;P&gt;-depending on your method for allowing the hosts, (eg ip address) it may be hard to manage the hosts &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Generally I don't think it's a great idea, but in reality it will likely work. The password will be cached on the ccp so i don't expect a huge number of requests back to the vault.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But I have to ask why, and is there a better solution? &lt;/P&gt;</description>
    <pubDate>Wed, 09 Oct 2024 16:35:39 GMT</pubDate>
    <dc:creator>Mal</dc:creator>
    <dc:date>2024-10-09T16:35:39Z</dc:date>
    <item>
      <title>CCP Password Retrieval Call</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/ccp-password-retrieval-call/m-p/1302815#M6008</link>
      <description>&lt;P&gt;I want to retrieve the password using CCP in more than 1000 of servers concurrently. Do you think there would be any good/bad consequences? or any cautious suggestions here&lt;/P&gt;</description>
      <pubDate>Wed, 09 Oct 2024 16:14:03 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/ccp-password-retrieval-call/m-p/1302815#M6008</guid>
      <dc:creator>Sanzu</dc:creator>
      <dc:date>2024-10-09T16:14:03Z</dc:date>
    </item>
    <item>
      <title>Re: CCP Password Retrieval Call</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/ccp-password-retrieval-call/m-p/1302816#M6009</link>
      <description>&lt;P&gt;-Check licencing - your licence may be per host accessing CCP.&lt;/P&gt;&lt;P&gt;-Make sure ccp is properly spec'd and configured. Otherwise it will be DOS'd by that number lf connections. &lt;/P&gt;&lt;P&gt;-depending on your method for allowing the hosts, (eg ip address) it may be hard to manage the hosts &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Generally I don't think it's a great idea, but in reality it will likely work. The password will be cached on the ccp so i don't expect a huge number of requests back to the vault.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But I have to ask why, and is there a better solution? &lt;/P&gt;</description>
      <pubDate>Wed, 09 Oct 2024 16:35:39 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/ccp-password-retrieval-call/m-p/1302816#M6009</guid>
      <dc:creator>Mal</dc:creator>
      <dc:date>2024-10-09T16:35:39Z</dc:date>
    </item>
    <item>
      <title>Re: CCP Password Retrieval Call</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/ccp-password-retrieval-call/m-p/1302817#M6010</link>
      <description>&lt;P&gt;All excellent points. To add to them, &lt;A alt="https://docs.cyberark.com/credential-providers/latest/en/content/hometileslps/lp-tile5.htm?tocpath=Performance%7C_____0" href="https://docs.cyberark.com/credential-providers/latest/en/content/hometileslps/lp-tile5.htm?tocpath=Performance%7C_____0" target="_blank"&gt;CyberArk has provided some benchmarks and recommendations&lt;/A&gt;.&lt;/P&gt;</description>
      <pubDate>Wed, 09 Oct 2024 16:41:04 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/ccp-password-retrieval-call/m-p/1302817#M6010</guid>
      <dc:creator>tim_schindler</dc:creator>
      <dc:date>2024-10-09T16:41:04Z</dc:date>
    </item>
    <item>
      <title>Re: CCP Password Retrieval Call</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/ccp-password-retrieval-call/m-p/1302818#M6011</link>
      <description>&lt;P&gt;-- CCP is properly specified and configured, and I am reviewing as per Tim posted articles too. I am thinking to architect in different way now. Would you be able to suggest different way where there won't be load on CCP ?&lt;/P&gt;&lt;P&gt;-- Yes, I am quite confused which auth method will be useful for this task. I came to know single app handles only 100s of IPs and anyway ip auth is not viable method as far i believe.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Oh well. I am still researching better solution for this.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 09 Oct 2024 17:55:08 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/ccp-password-retrieval-call/m-p/1302818#M6011</guid>
      <dc:creator>Sanzu</dc:creator>
      <dc:date>2024-10-09T17:55:08Z</dc:date>
    </item>
    <item>
      <title>Re: CCP Password Retrieval Call</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/ccp-password-retrieval-call/m-p/1302819#M6012</link>
      <description>&lt;P&gt;It's not really about the number of servers. It's about the requests per second. If an app on 1000 servers is only communicating with the CCP once a day then that load is negligible, even if they all hit the CCP at the exact instance. You'll get a spike of resource utilization and then it'll go back to idle. This link: https://docs.cyberark.com/credential-providers/latest/en/content/common/benchmark-cps-ccps-env.htm?tocpath=Performance%7C_____4#Requestspersecond Shows the testing that we were able to sustain 1k requests per second for an extended period of time. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In short, the number of servers/apps means almost nothing. It's all about the rate of requests. &lt;/P&gt;</description>
      <pubDate>Fri, 11 Oct 2024 01:30:49 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/ccp-password-retrieval-call/m-p/1302819#M6012</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2024-10-11T01:30:49Z</dc:date>
    </item>
    <item>
      <title>Re: CCP Password Retrieval Call</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/ccp-password-retrieval-call/m-p/1302820#M6013</link>
      <description>&lt;P&gt;I tried testing after your comments and above comments done by Mal and Tim. In 7 Seconds, we could fetch password in all 1000 servers in sequential order, but while fetching password parallelly, It literally took around 1 min 6 sec with minimal resources such as RAM and other resources in our environment. &lt;/P&gt;</description>
      <pubDate>Fri, 11 Oct 2024 21:42:34 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/ccp-password-retrieval-call/m-p/1302820#M6013</guid>
      <dc:creator>Sanzu</dc:creator>
      <dc:date>2024-10-11T21:42:34Z</dc:date>
    </item>
    <item>
      <title>Re: CCP Password Retrieval Call</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/ccp-password-retrieval-call/m-p/1302821#M6014</link>
      <description>&lt;P&gt;Any idea what would be the pros and cons of load balancing CCP @Malcolm Murray​&amp;nbsp;@Tim Schindler​&amp;nbsp;@Darren Khan​&amp;nbsp;@Malhar Vora​&amp;nbsp;@Pete Maan​&amp;nbsp;. Thank You all for helping and sharing experiences and expert knowledge over here. &lt;/P&gt;</description>
      <pubDate>Fri, 11 Oct 2024 21:44:19 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/ccp-password-retrieval-call/m-p/1302821#M6014</guid>
      <dc:creator>Sanzu</dc:creator>
      <dc:date>2024-10-11T21:44:19Z</dc:date>
    </item>
    <item>
      <title>Re: CCP Password Retrieval Call</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/ccp-password-retrieval-call/m-p/1302822#M6015</link>
      <description>&lt;P&gt;Pros:&lt;/P&gt;&lt;P&gt;Ability to handle one server being down, technically double the number of requests you can handle (vault and overhead does affect this).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Cons:&lt;/P&gt;&lt;P&gt;Need to configure ccp to ignore the load balancer header (easy to do). &lt;/P&gt;&lt;P&gt;Two cp client licences used. &lt;/P&gt;&lt;P&gt;Harder to diagnose issues. &lt;/P&gt;</description>
      <pubDate>Fri, 11 Oct 2024 22:05:27 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/ccp-password-retrieval-call/m-p/1302822#M6015</guid>
      <dc:creator>Mal</dc:creator>
      <dc:date>2024-10-11T22:05:27Z</dc:date>
    </item>
    <item>
      <title>Re: CCP Password Retrieval Call</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/ccp-password-retrieval-call/m-p/1302823#M6016</link>
      <description>&lt;P&gt;Thank You. Very last question of this thread. Just configuring in web.config in each CCP to ignore the LB header is just the step? &lt;/P&gt;</description>
      <pubDate>Tue, 15 Oct 2024 15:31:37 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/ccp-password-retrieval-call/m-p/1302823#M6016</guid>
      <dc:creator>Sanzu</dc:creator>
      <dc:date>2024-10-15T15:31:37Z</dc:date>
    </item>
    <item>
      <title>Re: CCP Password Retrieval Call</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/ccp-password-retrieval-call/m-p/1302824#M6017</link>
      <description>&lt;P&gt;IIS is the bottleneck there. I'm not sure if default IIS resource settings are limited. I have more knowledge in things like nginx but I would see if you could give more resources to the IIS processes. &lt;/P&gt;</description>
      <pubDate>Wed, 16 Oct 2024 16:06:54 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/ccp-password-retrieval-call/m-p/1302824#M6017</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2024-10-16T16:06:54Z</dc:date>
    </item>
    <item>
      <title>Re: CCP Password Retrieval Call</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/ccp-password-retrieval-call/m-p/1302825#M6018</link>
      <description>&lt;P&gt;@Malcolm Murray​'s list is perfect. &lt;/P&gt;</description>
      <pubDate>Wed, 16 Oct 2024 16:08:44 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/ccp-password-retrieval-call/m-p/1302825#M6018</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2024-10-16T16:08:44Z</dc:date>
    </item>
  </channel>
</rss>

