From what I can tell, weblogic seems to load some classes from the com.RSA.jsafe
that are potentially unsigned or has a different signature than the classes that
are loaded from jsse jar. This happens only when weblogic's SSL port is enabled.
Anyone know how to get around this? The only way I was able to get around this
is by specifying
"com.sun.net.ssl.internal.ssl.Provider" as the first security provider in the
java.security file but I would like to avoid this, if possible.
java.security.NoSuchAlgorithmException: class com.sun.net.ssl.internal.ssl.JSA_RSAKeyFactory
configured for KeyFactory(provider: null) cannot be accessed.
class "COM.rsa.jsafe.SunJSSE_aa"'s signer information does not match signer information
of other classes in the same package
at com.epiphany.shr.push.webserver.JsseListener.newServerSocket(JsseListener.java:165)
at com.epiphany.shr.push.webserver.BaseListener.start(BaseListener.java:302)
at com.epiphany.shr.push.webserver.SocketListener.start(SocketListener.java:64)
at com.epiphany.shr.push.webserver.HttpServer.start(HttpServer.java:111)
at com.epiphany.shr.push.webserver.HttpServer.startHttpServer(HttpServer.java:45)