I have a simple 1 step test that does a login. For whatever reason, this particular test uses TLS1.0 when it creates a connection to our site. I know that the Synthetic node is updated and able to use TLS1.2, because it uses it for many other tests. I also know that our webserver is setup to use 1.2, when you hit it with a normal browser it uses TLS1.2 by default.
Does anyone know why Synthetic would not automatically use 1.2, or a way to force it to?
Answer by Vaughn P. ·
support case submitted to dynatrace but adding comments into this post:
The reason the test is using the TLS 1.0 as the MN PA currently has FF24 browser agent which only support TLS 1.0 so if you have site with TLS 1.1 or 1.2 support it will downgrade to next supported TLS version. See below TLS support based on browser versions.
I would recommend upgrading the MN PA to the latest IE11, FF38 and CH46 browser agents that support TLS 1.1 and 1.2. The upgrade downtime is typically 3-4 hours so please advise best time. We prefer early business hours as after 5PM can be a challenge.
Answer by Bill H. ·
The reason why only that test is having an issue is that it may be running from a different browser agent than the others. If this test is running from an FF Agent, add the following in the first step using control target window to correct this issue:
var prefs = Components.classes["@mozilla.org/preferences-service;1"].getService(Components.interfaces.nsIPrefBranch);
Please let us know if this resolves your issue. If not, the next step would be to create a support ticket to investigate further with the test name. Thanks for your inquiry!
Saving script to GPN failed error 1 Answer