We want our browser monitor to run with the current user's credentials (windows-authentication).
When we record or play the clickpath -> it works fine!
When the synthetic instance runs (from a private location) it fails on authorization, as the windows login credentials are those that are required.
I've seen similar posts around this issue answered by the Credentials Vault feature, but that does not apply to this use case of windows credentials.
How can we make the private synthetic use the current user's windows credentials?
this is how it's done manually:
Is this something we can configure in config.properties perhaps?
Solved! Go to Solution.
Have you already tried adding 'basic authentication'? This option allows Chrome to perform the authentication in more situations than you might expect.
I'm afraid that's not what i had been asking about.
I want the synthetic to use the current user's windows credentials, without having to supply them myself at all.
This is an option that is configurable for chrome and i was wondering if there is a way to do so for the dt-synthetic embedded chrome as well..
Never done this, so these are hints:
You might also want to have a look at the following thread:
as @Antonio S. mentioned, for security reasons Dynatrace is using the LocalService account run the Synthetic service for private locations. (https://docs.microsoft.com/en-us/windows/win32/services/localservice-account) You might be able to achieve what you are asking for by changing the user of the Synthetic service, however we do not recommend this and it would be also changed back to LocalService during updates of the ActiveGate.
In general, we don't recommend using integrated authentication in combination with Synthetic. Mainly because it's likely you or other users want to use different users for different scenarios. The preferred way is what @Hannah M. mentioned.
May I ask which version of Chrome you are using locally as you mentioned recording/playback was working fine for you. As far as I'm aware Chrome disabled integrated authentication starting with version 81 (see https://www.chromium.org/developers/design-documents/http-authentication for details)
In case someone else is also facing this issue:
We we're able to overcome getting the synthetic test to run under our desired user by bypassing the Dynatrace Synthetic windows service-
We simply started the synthetic process from cmd (which was run by the logged in user) -
(you need to provide the .ini file located in the same folder)
Also, adding the --headless runs the chromium test without opening the browser.