- 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-25-2024 03:39 AM
Hi! I currently have a MacBook that has a policy applied to it to allow elevation of certain apps based on their publisher signature name. The MacBook is receiving the policy and acknowledging that it has it applied. However, the OS is still requiring that the user enters admin credentials. Has anyone seen this before? If so, what is the best way to resolve this issue?Thanks for your help!
Rob
10-25-2024 04:27 AM
Hi @Rob Mann , I'm still learning Mac and EPM (I'm a Windows guy), but I would guess that the app in question must need admin in order to run. I know that on Windows if you have an application in an Allow policy, but it tries to run as admin (either because the user forced it, or because it really needs it), you'll get the Windows UAC pop-up. And the screenshot you provided seems to be the equivalent on Mac.
Further looking at your screenshots, you have an application group with the publisher signature definition in it. But the group is named "Allowed" and I see in the GetPolicyInfo screenshot from the application that indeed a corresponding Allow (run) policy is being applied. So, this might just be as simple as you have the wrong kind of policy involved (since you say you intended to allow elevation). If that's the case, you need to put that publisher signature definition in an Elevate if necessary policy instead of an Allow policy.
Hope this helps!
-rwm
10-25-2024 06:56 AM
Hi,
I have the same issue on Windows on my side. Not on all devices but on few devices. I've opened a ticket for that. But it could be a global situation. Any news about CyberARK crew ?
10-25-2024 07:27 AM
Hi @Fethi ARRAS , since it's only a few devices it's definitely good you opened a support case for it. Most likely it is something unique to them.
The above said, there was a change in the 24.8 agent in how it integrated with Windows UAC. When you upgrade from an earlier agent to 24.8 or later (just the first time you upgrade) you will need to reboot the machine after the upgrade completes, or else users will get the UAC dialog when an application tries to elevate. Is it possible those few machines have recently upgraded from an agent prior to 24.8 to either 24.8 or later and haven't been rebooted since? We see this issue all the time because of this situation. You might want to ask the folks having the issue to try rebooting regardless, and see if that helps.
If the above is not the case, then the CyberArk Support team (the case you opened) is probably your best solution.
-rwm
10-26-2024 04:15 PM
Hi @Rob Mann ,
Joining to what @Ron Martin wrote (just to note macOS doesn't have elevate if necessary only elevate).
From the screen shot show you provided it seems you define an Allow policy and not an Elevate policy.
In Allow policy the agent let the OS "to decide" how it will be executed and in your case the the OS requested admin credentials.
Should you want to elevate it, make sure to define an elevate policy for this application.
You can see more details in our online docs here - https://docs.cyberark.com/epm/latest/en/content/policies/macospolicies-newui.htm
Thanks,
Arik.
11-06-2024 08:42 AM
Hi @Rob Mann
Since several community members answered your question, could you kindly share if any of these solutions resolved your issue?
If so, could you please mark the appropriate answer as "Select as Best" to assist other community members.
If the issue is still relevant, I would advise raising a ticket with our Support team for further assistance.
Thank you, Liad
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!

