![]() If your certificate will be issued by a your local CA and not by a public CA, then you might need to import the CA certificate into the trust store of the JVM you are running so the SSL connection to the gateway can be trusted. This is done via the CMC console in Dynatrace Managed, not by copying it to the host. So you should get a certificate with SNI extension, including a private key and put it on the ActiveGate. Now also with the SNI extension (subject alternative name). You will need a proper certificate issued to FQDN / DNS name of the ActiveGate. The default self-signed certificate is not a good way to operate Cluster ActiveGate (named Public Security Gateway in the past). Certificates are verified every time, it does not matter if it is a local connection. You have the answer right there - ": No subject alternative names". The java application is run on the same machine as the PAG so I don't understand why there should be a problem with the certificate, but that is just my ignorance about certificates.Ĭan anybody help solving this issue, so I could test the openkit setup, before I let java developers access the setup ? I think that this certificate should be exported and then imported with keytools, but I can't find any documentation about how to do this. Is there a way in Dynatrace to export this certificate to other machines ? I have not altered anything about the certificate that the PAG uses, so it just states it has been issued by dynatrace. : : No subject alternative names presentĪt .getSSLException(Alerts.java:192)Īt .fatal(SSLSocketImpl.java:1946)Īt .fatalSE(Handshaker.java:316)Īt .fatalSE(Handshaker.java:310)Īt .serverCertificate(ClientHandshaker.java:1639)Īt .processMessage(ClientHandshaker.java:223)Īt .processLoop(Handshaker.java:1037)Īt .process_record(Handshaker.java:965)Īt .readRecord(SSLSocketImpl.java:1064)Īt .performInitialHandshake(SSLSocketImpl.java:1367) T10:52:46.245 ERROR HTTPClient sendRequest() - ERROR: STATUS Request failed! When I run the java application, I get errors about the cbruhn2]# java SimpleSample Then I have altered the SimpleSample for my environment stating the url in my environmen, the application the applicationid and deviceid. ![]() On the same server I have installed the java openkit package from If this happens to you, swapping back to Oracle's JDK may be your best solution.I have installed a Publice Active Gateway (PAG). Once I changed over to Oracle's JDK and ran the Retrofit tests, they all worked without errors. You can find the Oracle Java JDK location by typing echo $JAVA_HOME (Unix / MacOS) on the command line without any options. Uncheck this to allow you to put the path to your Oracle JDK here. File -> project properties, "SDK Location": You can choose the java version in the project properties. I thought perhaps swapping back to using the Oracle Java version would allow these tests to work. My installed Oracle Java version is: java version "1.8.0_162" I went into the Mac bundle for Android Studio 3.1.1 and found that the OpenJDK version was this: OpenJDK 1.8.0_152. When I first created these tests, they all worked fine now they show this when run: D/Retrofit: : : PKIX path validation failed: : Algorithm constraints check failed on signature algorithm: SHA256WithRSAEncryptionĪt .getSSLException(Alerts.java: 192)Īt .fatal(SSLSocketImpl.java: 1959)Īt .fatalSE(Handshaker.java: 302)Īt .fatalSE(Handshaker.java: 296)Īt .serverCertificate(ClientHandshaker.java: 1514)Īt .processMessage(ClientHandshaker.java: 216)Īt .processLoop(Handshaker.java: 1026)Īt .process_record(Handshaker.java: 961)Īt .readRecord(SSLSocketImpl.java: 1072)Īt .performInitialHandshake(SSLSocketImpl.java: 1385)Īt .startHandshake(SSLSocketImpl.java: 1413)Īt .startHandshake(SSLSocketImpl.java: 1397)Īt .io.nnectTls(RealConnection.java: 192) I have my Retrofit network tests in the (test) folder it is much easier and faster to run the tests on the computer. ![]() For my app, I have some Realm tests that must run in the on device (or emulator), as there isn't source or binaries for the computer. The on computer tests are in the (test) folder. The on device (or emulator) tests are in the (androidTest) folder. The source code goes into the non-test folder. I noticed that my network calls, while working on device / emulator, did not work under testing on my computer. I was running unit tests after the first stage of updates to my Java app in Android Studio 3.1.
0 Comments
Leave a Reply. |