Cannot change to Edge on PSM

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

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

Cannot change to Edge on PSM

L3 Networker

Hi everyone,

 

I am trying to onboard some web applications to my CBA. At first, i ran into this error:

 

I configured to use Edge

Field_Content_versions_oct20__068Vy00000ZPOivIAH.pngField_Content_versions_oct20__068Vy00000ZPOnlIAH.pngbut it was keep using the Internet Explorer 11. Then i found this article https://community.cyberark.com/s/article/How-to-change-PSM-WebApp-to-use-Edge

 

But when i follow this arrticle, it showed another error. Now when i connect to the web app, it shows nothing. Just loading and then signout.

Field_Content_versions_oct20__068Vy00000ZPPIPIA5.png 

Besides, the WebFormDispatcher. What should i enter the Formname value when the login page don;t have formname? The webpage is IBM QRadar SIEM, i was try deprecated but still not work.

 

Thanks!

 

 

1 accepted solution

Accepted Solutions

L3 Networker

Hi guys,

 

I manage to fix this problem myself along with your support.

 

I notice there is some point between the Connection Component that worked (PSM-WebApp-QRadar-Chrome) and the one that doesn't work (PSM-WebApp-QRadar).

 

Field_Content_versions_oct20__068Vy00000ZbRUyIAN.pngField_Content_versions_oct20__068Vy00000ZblLaIAJ.pngField_Content_versions_oct20__068Vy00000ZbmO5IAJ.png 

Field_Content_versions_oct20__068Vy00000Zbfw6IAB.png 

So i guess the problem is not about Formname value as the error message mention but more about the ClientDispatcher value

View solution in original post

8 REPLIES 8

L7 Applicator

Hi @Quang Le​ 

 

Can you please disable ‘Application Lock Window’ and try again.

 

Also please share PSM dispatcher logs for the exact errors you see when trying to establish the connection.

Hi @Malhar Vora​ ,

 

You mean this right?

 

Field_Content_versions_oct20__068Vy00000ZRKRVIA5.png 

Yes, after i change it to No. This error happen again.

Field_Content_versions_oct20__068Vy00000ZQkw4IAD.png 

So i guess the error below occur after i run the PSMConfigureAppLocker.ps1.

 

After disable the Lock Application Windows, yes it shows the first error about the WebFormDispatcher again.

  This is the pic about very first error

 

Field_Content_versions_oct20__068Vy00000ZR0JIIA1.png

L2 Linker

Can you also change the protocol to HTTP (instead of HTTPS).

It will still open HTTPS if your URL has been set to HTTPS

Yes, but i see it doesn't make any change to the errors that i am facing. Thank you, do you have any other suggestion?

L2 Linker

I assume you either restarted the the PSM service or waited around 15 minutes for it to take effect

Thank you but the same error Can't find requested form named

L3 Networker

Hi guys,

 

I manage to fix this problem myself along with your support.

 

I notice there is some point between the Connection Component that worked (PSM-WebApp-QRadar-Chrome) and the one that doesn't work (PSM-WebApp-QRadar).

 

Field_Content_versions_oct20__068Vy00000ZbRUyIAN.pngField_Content_versions_oct20__068Vy00000ZblLaIAJ.pngField_Content_versions_oct20__068Vy00000ZbmO5IAJ.png 

Field_Content_versions_oct20__068Vy00000Zbfw6IAB.png 

So i guess the problem is not about Formname value as the error message mention but more about the ClientDispatcher value

  • 1 accepted solution
  • 106 Views
  • 8 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!