- 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.
02-15-2024 02:56 AM
Hi @all,
We're developing more or less several PSM connection components ourselves.
We have our own development environment for tests and checks.
In the past we decided to have a clear documentation to create an own dispatcher for each component, version and deployment status.
So we ended up with about 380 connection components in the PVConfiguration.xml.
Now we've got some AppLocker issues as a result of so many configured connection components and we decided to clean up our components.
But now here is my question:
When we reach this number of components in the feature. Is it possible to split the connection component safe? To define that one psm group uses the PSMUniversalConnector safe A and the second group uses the PSMUniversalConnector safe B?
Best regards,
Sven
02-15-2024 03:12 AM
Are you referring to the PSMUniversalConnector safe?
02-15-2024 03:28 AM
Yes, it is. i've edit my question to clarify it. But never the less for my question it could be an own other safe as well.
02-15-2024 03:47 AM
I haven't seen a documented way to do this but it is a good idea for when you have different PSMs for different use cases.
02-15-2024 04:37 AM
How would you even configure one set of PSM's to use a safe not named "PSMUniversalConnectors"... I thought this is hard-coded somewhere in the PSM application.
02-15-2024 05:04 AM
I think thats the question summed up and from what I can see, you can't.
02-15-2024 05:41 AM
That's the question. Maybe someone has a problem or use case for this, and maybe a solution or workaround that I haven't thought of yet.
02-15-2024 05:59 AM
I think this needs to be logged as an enhancement request, as I don't believe the product supports this scenario and have never seen it discussed before.
Quite simply if a connector exists on CyberArk, all PSMs know about it and if the software is installed and the platform configured to use that PSM, it needs the Applocker rules. You could theoretically only apply Applocker rules to those PSMs in the farm which supports the app, but that would be messy longer term.
https://community.cyberark.com/s/enhancement-request-tabs for the Enhancement Requests.
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!

