Can't elevate DockerToolbox 19.03.1

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Can't elevate DockerToolbox 19.03.1

L1 Bithead

No matter which EPM policy i have defined to this app installation executable, it never gets it and never get elevated, all other software works fine.

It was tested on numerous computers (win10 OS), it of course works with LAR.

Only thing that is seems strange to me is that Publisher Status states "Signature not Trusted", but it does not suppose to cause EPM not to elevate this software installationField_Content_versions_oct20__068Ht00000QTcwAIAT.pngPFA this is how it looks even if i add this app install to a policy - keeps on being inside the GreyList.

Policy is still - Windows Main Default Policy.

We are using EPM SaaS latest version 23.4.0.1235.

Also i have tested this Software with EPM-On-Prem agent 11.5.5.102 and added it to Elevated Policy and it worked without issues.

I feel like SaaS default policies needs some adjustment.

Thanks for whom can help.

9 REPLIES 9

L4 Transporter

it depends how you created the elevate policy. if you use the publisher attribute in the application definition and this publisher signature is not valid on the endpoint the policy will not be effective.

L1 Bithead

Hi @Yossi Dantes​

thank you for your reply, please explain what you mean.

For my case this is what i did:

I have tried a couple of measures by adding that to the predefined Elevate Applications Group:

  1. Name
  2. SHA1 & SHA256
  3. Publisher
  4. Original Name
  5. File Name

sometimes all of them, sometimes only 2 of them, sometimes only 1 of them but nothing changed.

Any ideas?

are you sure the agent received the policy? when you right click on the agent icon -> about, does it seems the agent get policies lately?

I'm sure! this is not my first rodeo 🙂

Thank you @Yossi Dantes​  for helping out!

according to the screenshot you attached the EPM agent doesn't apply the policy you defined on the DockerToolbox-19.03.1.exe file. if you absolutely sure you defined the policy correctly and target it to the correct endpoint/user, please collect agent logs and open a case with customer support.

L2 Linker

We faced the same issue with another application called OfficeTimelinePro. The root cause turned out that the publisher certificate on the executable and the certificate installed on the OS had different thumprints. One thing to keep in mind is that a visual inspection of the certificate chain on the OS does not indicate a problem. It's only when you notice the finer details and look at the thumbprint specifically, then you start noticing the difference.

 

In our case, including the "Publisher" criteria while creating the application definition never worked for that application. We could only get that application to elevate with a broad definition.

 

You could try running this command and attach it to your support case - C:\Program Files\CyberArk\Endpoint Privilege Manager\Agent\vf_agent.exe -DumpFileInfo "<<path of Docker Toolbox>>" c:\temp\output.txt

Thanks @Nikhil Rao​  - i will do that!

Appreciate the help.

Good Advice @Nikhil Rao​ 

L0 Member

Is there a way we can find the publisher status remotely rather than going into the endpoint?

  • 255 Views
  • 9 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

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!