Having some strange problems with Selenium connection component

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

Having some strange problems with Selenium connection component

L4 Transporter

Hi,

 

This is a followup to an earlier thread about using the Selenium-based connection component with PSM and web access:

 

https://community.cyberark.com/s/feed/0D52J00006VEhmW

 

I am testing with a rather simple web page that has a username and password field. I *think* that my connection component is kind of working but I am noticing some problems:

 

  • Even though I specify that the page should not be fullscreen, when then login occurs, the resulting web page appears as fullscreen, with no scroll bar or address bar. I cannot seem to get it to be non-fullscreen WITH scrollbar and address bar, i.e., the connection component doesn't appear to obey those parameters.

 

  • AFTER the login occurs, I am getting these popups:

 

0682J00000661qJQAQ.jpg

 

 

Does anyone know how to resolve the above problems?

 

Also, I am currently running CyberArk 10.3, but am planning to make a new development environment with 10.6.1. Does the Selenium component work better in 10.6.1?

 

Thanks,

Jim

 

EDIT 1: Also, in the PSM logging, I see references to a parameter named "EnableTrace" which is not present. What is that parameter, and where do I put it in the connection component? I am hoping that might provide more detailed logging?

8 REPLIES 8

L3 Networker

@James Lum​ Add EnableTrace to Client Specific. With EnableTrace=Yes, you may not notice the Progress Bar (Connecting...).

L4 Transporter

@Karthik Javvaji​ 

 

Thanks I will try that.

 

Any ideas about the other popup? Is that happening just because something is taking too long? If so, what parameter might control that (so that I can try to increase it)?

 

Thanks again,

Jim

L3 Networker

Which Browser (IE\Chrome) are using for the connection component ? For the other the timeout might be occurring as the connector can't find the username field. Check the dispatcher log.

You can also try latest version of PLUGIN GENERATOR UTILITY (PGU) available in marketplace to generate PSM Web Connectors.

L4 Transporter

@Karthik Javvaji​ 

I added the EnableTrace, but that didn't seem to change anything (either in the logging or the overall behavior). I still get the same popups, etc.

 

FYI, I am using Chrome in the connection component.

 

Also, here's a snippet of the PSM logging:

 

[08/01/2019 | 17:08:44] | :: | PSMDU019I Dispatcher trace message: [Chrome :: DeletePreviousFolder -> Searching for previous session temp folder 'C:\Users\TEMP.BANA1.014\AppData\Local\Temp\PSMChromeData\PSM-0200000000000000\7'] [08/01/2019 | 17:08:44] | :: | PSMDU019I Dispatcher trace message: [WebFormDispatcher :: ExecuteLoginLogic -> START] [08/01/2019 | 17:08:44] | :: | PSMDU019I Dispatcher trace message: [Chrome :: Init -> Active session's temporary directory is C:\Users\TEMP.BANA1.014\AppData\Local\Temp\PSMChromeData\PSM-0200000000000000\7] [08/01/2019 | 17:09:02] | :: | PSMDU019I Dispatcher trace message: [Selenium :: OpenWebBrowser -> The browser was initialized successfully.] [08/01/2019 | 17:09:04] | :: | PSMDU013I Received a request from dispatcher [SendPID] [08/01/2019 | 17:09:04] | :: | PSMDU046I Sent PID of the dispatched process to PSM. PID: 7828 [08/01/2019 | 17:09:04] | :: | PSMDU015I Successfully performed dispatcher's request [SendPID] (result=[0]) [08/01/2019 | 17:09:04] | :: | PSMDU019I Dispatcher trace message: [WebFormDispatcher :: WaitForFirstElement -> START] [08/01/2019 | 17:09:04] | :: | PSMDU019I Dispatcher trace message: [WebFormDispatcher :: WaitForFirstElement -> Waiting for the first element 'UserEmail'.] [08/01/2019 | 17:09:04] | :: | PSMDU019I Dispatcher trace message: [Selenium :: WaitForElement -> Waiting until element 'UserEmail' is found in page. Timeout: '100'.] [08/01/2019 | 17:09:05] | :: | PSMDU019I Dispatcher trace message: [Selenium :: WaitForElement -> Element 'UserEmail' was found in new page.] [08/01/2019 | 17:09:05] | :: | PSMDU019I Dispatcher trace message: [WebFormDispatcher :: WaitForFirstElement -> END] [08/01/2019 | 17:09:05] | :: | PSMDU019I Dispatcher trace message: [WebFormDispatcher :: Logon -> START] [08/01/2019 | 17:09:05] | :: | PSMDU019I Dispatcher trace message: [Selenium :: FindObject -> Trying to find element 'UserEmail' in page. ] [08/01/2019 | 17:09:05] | :: | PSMDU019I Dispatcher trace message: [Selenium :: FindObject -> Element 'UserEmail' found by 'ID'.] [08/01/2019 | 17:09:05] | :: | PSMDU019I Dispatcher trace message: [Selenium :: EnterTextToObject -> Sending input to element 'UserEmail'.] [08/01/2019 | 17:09:13] | :: | PSMDU019I Dispatcher trace message: [Selenium :: EnterTextToObject -> Input was sent successfully to element. ] [08/01/2019 | 17:09:13] | :: | PSMDU019I Dispatcher trace message: [Selenium :: FindObject -> Trying to find element 'UserPass' in page. ] [08/01/2019 | 17:09:14] | :: | PSMDU019I Dispatcher trace message: [Selenium :: FindObject -> Element 'UserPass' found by 'ID'.] [08/01/2019 | 17:09:14] | :: | PSMDU019I Dispatcher trace message: [Selenium :: EnterTextToObject -> Sending input to element 'UserPass'.]

From the above, I think that it is finding the username and password fields, and sending values, so I am still not sure where the timeout is occurring.

 

The funny thing is the popups occur and then disappear, and then a long while later, the blank fullscreen webpage appears (and then eventually disappears).

 

"Scratching my head" :(....

 

Jim

 

 

L3 Networker

At this point it is better to open a support case.

Meanwhile can you try with the PLUGIN GENERATOR UTILITY (PGU) to generate PSM Web Connectors and compare with the connection component in the PVWA ?

L4 Transporter

Hi,

 

I am fairly new with CyberArk, so I haven't opened a case before, but I may try that, but before I do that, I just did a test and clicked the show detail on the RDP popup and it displayed the Windows session and said "Preparing Windows" and then I got the timeout popup. So I think that it may be taking a long time to create the local Windows session (within which the browser runs), so can you (or anyone else) identify where that timeout is set?

 

I am working from a remote location for the next several months, so I don't have my regular dev environment, but rather a kind of slimmed down environment (basically a laptop), which is probably less performant, so maybe that is why this is happening (i.e., so taking longer for things to happen), so I would like to identify where I can adjust the timeout to get this working.

 

Thanks,

Jim

L3 Networker

You can adjust the timeout for ActionTimeout and PageLoadTimeout, but again not sure whether it makes any difference.

Hi, can you please tell how EnableTrace affect the connecting progress bar issue. Recently fixed similar issue by this

  • 1536 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!