- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
10-09-2024 09:14 AM
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
10-09-2024 09:35 AM
-Check licencing - your licence may be per host accessing CCP.
-Make sure ccp is properly spec'd and configured. Otherwise it will be DOS'd by that number lf connections.
-depending on your method for allowing the hosts, (eg ip address) it may be hard to manage the hosts
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.
But I have to ask why, and is there a better solution?
10-09-2024 09:35 AM
-Check licencing - your licence may be per host accessing CCP.
-Make sure ccp is properly spec'd and configured. Otherwise it will be DOS'd by that number lf connections.
-depending on your method for allowing the hosts, (eg ip address) it may be hard to manage the hosts
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.
But I have to ask why, and is there a better solution?
10-09-2024 09:41 AM
All excellent points. To add to them, CyberArk has provided some benchmarks and recommendations.
10-09-2024 10:55 AM
-- 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 ?
-- 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.
Oh well. I am still researching better solution for this.
10-10-2024 06:30 PM
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.
In short, the number of servers/apps means almost nothing. It's all about the rate of requests.
10-11-2024 02:42 PM
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.
10-11-2024 02:44 PM
Any idea what would be the pros and cons of load balancing CCP @Malcolm Murray @Tim Schindler @Darren Khan @Malhar Vora @Pete Maan . Thank You all for helping and sharing experiences and expert knowledge over here.
10-11-2024 03:05 PM
Pros:
Ability to handle one server being down, technically double the number of requests you can handle (vault and overhead does affect this).
Cons:
Need to configure ccp to ignore the load balancer header (easy to do).
Two cp client licences used.
Harder to diagnose issues.
10-15-2024 08:31 AM
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?
10-16-2024 09:06 AM
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.
10-16-2024 09:08 AM
@Malcolm Murray's list is perfect.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!

