For generating the Testid we are calling the RestAPI by passing parameters in Json using some poweshell scripts this was working fine with out any issues in 6.2 version.
But after upgrading to 6.3 facing issues in calling the RESTAPI this is because of some Dynatrace CA cetificate.
in 6.2 we it was not scecured where as in 6.3 its scecured.i,e calling using HTTPS.
Can you please let me know how to access it using HTTP or else let me know how to fix the problem.
Answer by Sonja C. ·
there is a new default setting which is set by default "accept authentication data only with HTTPS" - which you will need to uncheck to get back to HTTP for the rest api (requiring authentication).
Answer by Guenter H. ·
OK, it was documented (in bold) on Server REST Interfaces, where it applies. (Client REST is an entirely different thing.)
I added a warning though to the top of the Services - Management Tab page where the setting (Accept authentication data only via HTTPS) is described.
More so, due to this issue, I added an entirely new page Breaking Changes to the documentation (deliberately placed right under the Upgrade and Migration Guide sub-tree), where I will collect breaking changes. (different defaults,...)
I think such a page is long overdue and input is welcome.
Hope this helps
Answer by Guenter H. ·
Hey Joe and Sravan @shafizhatta,
just talked to engineering (Mike and Wolfgang).
Wolfgang thought to remember a way to ignore the cert in the Jenkins plugin, but that´s an RFE. I´ll poke the lead engineer on the issue.
So currently you either
auth data over http (uncheck the above mentioned box) or
import the Dynatrace cert into the Jenkins keystore or
use a trusted (as opposed to a self-signed) certificate and keys which should be automatically accepted.
I will document this.
Answer by Joseph H. ·
Prior to upgrading to 6.3, my Jenkins environment was configured to use HTTPS/8021. After upgrading the REST calls quit working. Switching back to HTTP/8020 and unchecking the box resolved the problem, but the bigger question is why didn't HTTPS continue to work? I'm suspicious it has something to do with the certificates we're shipping which are not liked by most systems. Can you confirm this to be the underlying cause of HTTPS no longer working on the REST calls after upgrading to 6.3?