Bypass Chrome authentication pop-up in a Synthetic browser monitor

Platform Synthetic Monitoring
,
1

Is there a way to bypass the Chrome authentication pop-up in a Synthetic browser monitor? For lack of a better way of saying this…can this be “hacked” or bypassed with JavaScript as another synthetic step prior to accessing the application? I’ve seen references for using WebDriver in Selenium; I just didn’t know if this was possible, and if so, how, in the new DT Synthetic this would work. Chrome Authentication PopUp.pptxDynamics 365 Performance.pptx
chrome-authentication-popup.pptx (224 KB)

2

You can add the credentials for the pop up into the Authentication section of the Navigate event. There’s more information on this here.
Best wishes, Hannah

3

I’m aware of that however it doesn’t work.

4

I thought about what you suggested and tested it. It does work. Thank you.

5

That’s excellent news. Thanks for the update.

6

Hi Folks,

I have the same issue at one of my clinet’s company sharepoint site. I have already registered a user in the vault and set the html authentication in the first navigate action. Palyback is works fine but the scheduled runs are failed and I do not know why. I guess the sts login iframe pop up is the issue, but I do not have idea how to solve it.

Here is the successful playback:

Mizs_0-1662367615455.png
Mizs_0-1662367615455.png1350×804 53.9 KB

Here is the scheduled run results, the error message always the same:

Mizs_1-1662367702707.png
Mizs_1-1662367702707.png1581×574 29.6 KB

Thanks in advance for your help.

Br, Mizső

7

Edit: this experimental property is no longer available. Removing comment to prevent confusion.

8

Hi HannahM,

Thanks very much I’m going to try it.

Best regards, Mizső

9

Hi HannahM,

This property did not help. I had to try somthing elese, becasue it was very suspicious which is related with login.microsoftonline.com:

In case of use the scheduled engine it alwasy get 401 see below, we have tried to check the site outside the DT in an incognito window, this suspicious request had 200. My colleasue has an idea, maybe there is a protection at MS against robots. So we have added a user agent configuration in the device emulation settings. New user agent is:

Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/104.0.0.0 Safari/537.36

Now the scheduled runs availabilty is 100%. It seems everything is fine and there is not “1701 - The specified target window was not found” error, however the login.microsoftonline.com request is still 401. :slightly_smiling_face:

Before user agent change:

Mizs_0-1662571227198.png
Mizs_0-1662571227198.png1325×800 60.6 KB

After user agent change:

Mizs_1-1662572291229.png
Mizs_1-1662572291229.png1837×580 117 KB

Thank you very much for your help.

Br, Mizső

10

That’s great, thanks for the update.

11

Hello Hannah,

Is there a workaround to override the user-agent used by the browser monitor?

we are running into an issue while logging in to the application (which we have not control) as it is blocking the user-agent used by the browser monitor. The scriptConfig has a userAgent field,  but I see the docs mention the RuxitSynthetic/1.0 is appended regardless

12

Hi @abhijeet-allu , no there is no way to prevent RuxitSynthetic/1.0 from being appended to the User Agent string.

I recommend that you vote for this Production Idea, Exclude RuxitSynthetic in custom user agent, and add a comment mentioning why this is important for your testing.