Skip to content

Tag: ssl

How do I get OpenJDK 16 to talk with an SSL enabled nginx server?

I’m running a spring boot application that needs to make an https call to an nginx server. The application is running on CentOS 7 with OpenJDK 16. Following this more or less, I gathered a list of all the ciphers available to the JVM: In nginx, I have the following: I’ve tried every one of the ciphers available to my

SSL Handshake error after Client Finished handshake message

I’m attempting to perform mutual TLS authentication to (changed), and I’m getting Fatal (HANDSHAKE_FAILURE): Couldn’t kickstart handshaking, readHandshakeRecord after Produced client Finished handshake message. I am using AdoptOpenJDK JVM options: Code I use for debugging this problem: Logs with handshake steps successfully performed: Just after that I get: The same request sent with curl or openssl is

SSL for JMX with RMI

We have a Java application which has had a JConsole connection with password authentication for a while. In improving the security of this, we are trying to encrypt the connection made from JConsole to the application. Up until now, we have launched our application with the following launch command: With this, we can flawlessly access the JMX methods of MyApplication

How can i solve [Received fatal alert: bad_certificate]?

I’ve created two servers locally, and I’m going to apply a mutual authentication to their communication. I just don’t know what the problem is. I lack understanding of this mechanism, but I also lack understanding of the server itself. Create each key store Export to X.509 to register certificate in Truststore. Register each other’s certificates in Truststore. server’s client’s

Communication link failure in mysql jdbc driver

I’am not able to establish connection with mysql from java using this code It’s throwing me this error The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server. The driver has not received any packets from the server. No appropriate protocol (protocol is disabled or cipher suites are

Certificate subject for doesn’t contain a common name and does not have alternative names

I have generated a SSL self-signed certificate using the following commands one-by-one in remote ubuntu machine via terminal: T I’ve added the server.crt onto my local machine’s cacerts using keytool in command prompt as admin. Also added the server.crt onto ‘Trusted Root Certification Authorities’. he issue is that HTTPS request to the remote ubuntu machine server on Postman works fine