How can I get Microsoft Edge 64 bits published on PSM server?

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

How can I get Microsoft Edge 64 bits published on PSM server?

L3 Networker

Hi,

 

we do have our PSM servers working fine and we used them to connect via RDP (Connection component PSM-RDP). Everything is good.

 

We would need now to publish Microsoft Edge 64 bits to enable us to start a PSM hosted Microsoft Edge that will be using our Vaulted Credentials.

 

Therefore I have:

a) Deployed Microsoft Edge 64 bits on the PSM server

b) Deployed Microsoft Edge Driver (same version) in components/x64

c) Change Applocker file (XML) to have both Edge (method publish) and EdgeDriver (method hash)

d) Ran the applocker powershell script

e) I have duplicated PSM-WebAppSample connection compoent

f) Change the duplicated Connection Component to Edge including adding new parameter BrowserPath

 

Result:

 

RDP file get created, executation start, connect to PSM server host then no error and suddenly logout. No error message at least timely visible, no popup windows with an error code.

 

Any thoughts?

How can we see what the PSM is doing when he got such connection?

 

6 REPLIES 6

L7 Applicator

You could try the latest driver framework

https://community.cyberark.com/marketplace/s/#a35Vy0000014I93IAE-a39Vy00000526knIAA

 

What is the browser path you have used ?

 

I'd expect logs to be in the components directory under logs and/or psmconsole / psmtrace

 

 

 

I have installed the latest driver framework already for 32 bits and 64 bits.

 

BrowserPath is : C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe

 

L4 Transporter

Hi Diego,

 

Do you have specific events in windows event viewer? Sometimes specific errors are written here.

 

do you follow this guide? https://docs.cyberark.com/pam-self-hosted/latest/en/content/pasimp/psm_webapplication.htm

Since you are using Edge 64-bit, your PSM is almost certainly using the 64-bit WebAppDispatcher. For the 64-bit dispatcher to work, all the files from the Components folder of the Secure Web Application Connectors Framework package must be copied to a specific subfolder.

 

Correct path: C:\Program Files (x86)\CyberArk\PSM\Components\x64\Connectors

 ensure msedgedriver.exe and all other DLLs from the package are in this x64\Connectors folder, not just in the main Components folder.

 

In your duplicated connection component, go to Target Settings > Client specific settings.

 

Verify that you have added a parameter named BrowserPath.

 

Set its value to the full path of the Edge 64-bit executable, for example: C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe

 

Can you add the parameter "EnableTrace=true" in client specific settings. The enable trace displays browser during logon process.

Do you have the same error with Chrome for example?

 

Also make sure that ClientApp is Edge

Already set to "Edge" within the Target Settings

In the event log I see the following:

 

/*

PSMSR126E [bc628122-7624-410a-b960-fb4af3e12308] Failure occurred while handling session. PSMSR133E [bc628122-7624-410a-b960-fb4af3e12308] Failed to create process "C:\Program Files (x86)\CyberArk\PSM\Components\x64\\CyberArk.PSM.WebAppDispatcher.exe". Code: 1260 (Codes: -1, -1)

*/

 

What I see there is a double "\\" before the "CyberArk.PSM.WebAppDispatcher.exe". I do not see any folder called "Connectors" (C:\Program Files (x86)\CyberArk\PSM\Components\x64\Connectors)

 

BrowserPath is set to "C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe".

 

I have added "EanbleTrace" and will check if I have better information.

 

We do not use "Chrome" in our company.

 

 

 

 

  • 65 Views
  • 6 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!