Mgiyuk

Weblogic/Java not sending Client Certificate in Mutual SSL Integration with IIS I'm having trouble understanding why Weblogic/Java are not sending the Client certificate requested by the server(IIS server) during SSL Handshake via the CertificateRequest message. I have already checked and tried all the other questions/answer in SO such as : Java not providing client certificate for mutual SSL? and similar. I have created a custom keystore called Identity.jks and I've follwed the WL guides (and everything else I could find on the Internet) to do the right settings. Here are the debug logs for the SSL handshake: *** CertificateRequest Cert Types: RSA, DSS, ECDSA Supported Signature Algorithms: SHA512withRSA, SHA512withECDSA, SHA256withRSA, SHA384withRSA, SHA1withRSA, SHA256withECDSA, SHA384withECDSA, SHA1withECDSA, SHA1withDSA Cert Authorities: <Empty> *** ServerHelloDone Warning: no suitable certificate found - continuing without client authentication *** Certificate chain...

Error running Maven project: Unsupported protocol: t3 I have a Maven project for monitoring of weblogic servers through JMX. In the maven POM.xml , I specify the dependency for wlfullclient.jar through scope tag due to previous errors. POM.xml wlfullclient.jar scope <dependency> <groupId>weblogic</groupId> <artifactId>wlfullclient</artifactId> <scope>system</scope> <systemPath>${basedir}/libs/wlfullclient-11.1.1.4.0.jar</systemPath> <version>11.1.1.4.0</version> </dependency> It builds successfully, however, when running the jar file, I get this error: jar java.net.MalformedURLException: Unsupported protocol: t3 at javax.management.remote.JMXConnectorFactory.newJMXConnector(Unknown Source) at javax.management.remote.JMXConnectorFactory.connect(Unknown Source) I looked into the MANIFEST file in the built jar file, and noticed it lists all jars in the classpath, except this wlfullclient...