My Oracle Support Banner

OPSS - Server Unable To Comeup Due To Java.security File Changes -java.lang.NoClassDefFoundError: javax/crypto/BadPaddingException (Doc ID 2124180.1)

Last updated on APRIL 12, 2016

Applies to:

Oracle Platform Security for Java - Version 11.1.1.4.0 and later
Information in this document applies to any platform.

Symptoms

 

Server unable to comeup due to java.security file changes.

Run the server with SunJCE as the crypto provider and hence removed the highlighted entry below (com.rsa.jsafe.provide.JsafeJCE) in java.security file. But after the change, the server doesn’t start and failing with the error below. Please advice.

Java.security Entry

security.provider.1=sun.security.provider.Sun
security.provider.2=com.rsa.jsafe.provider.JsafeJCE  <<<<<<<<<<<<<<<<
security.provider.3=sun.security.rsa.SunRsaSign
security.provider.4=com.sun.net.ssl.internal.ssl.Provider
security.provider.5=com.sun.crypto.provider.SunJCE
security.provider.6=sun.security.jgss.SunProvider
security.provider.7=com.sun.security.sasl.Provider
security.provider.8=org.jcp.xml.dsig.internal.dom.XMLDSigRI
security.provider.9=sun.security.smartcardio.SunPCSC

 

Error reported in the WL diagnostic file:

<Mar 11, 2016 2:54:46 PM EST> <Error> <Security> <BEA-090892> <The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: javax/crypto/BadPaddingException>
<Mar 11, 2016 2:54:46 PM EST> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: javax/crypto/BadPaddingException
weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: javax/crypto/BadPaddingException
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1398)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1018)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
Truncated. see log file for complete stacktrace
Caused By: java.lang.NoClassDefFoundError: javax/crypto/BadPaddingException
at sun.security.rsa.RSASignature.engineVerify(RSASignature.java:175)
at java.security.Signature$Delegate.engineVerify(Signature.java:1140)
at java.security.Signature.verify(Signature.java:592)
at sun.security.x509.X509CertImpl.verify(X509CertImpl.java:441)
at sun.security.x509.X509CertImpl.verify(X509CertImpl.java:389)
Truncated. see log file for complete stacktrace

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.