My Oracle Support Banner

OPSS - Unable check the credentials seeing KeyStoreServiceException caused by bad padding error messages in the EM console (Doc ID 1983402.1)

Last updated on DECEMBER 22, 2023

Applies to:

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

Symptoms

Checking the credentials seeing bad padding error messages in the EM CONSOLE

1. Initially on Box1, set up the DB1 and Weblogic 10.3.6 + SOA 11.1.1.7.5 + Webcenter11.1.1.8 everything works fine
2. Sync the prod Database to DR database
3. Stop the DATAGUARD
4. In Box2, Install Weblogic 10.3.6 + SOA 11.1.1.7.5 + Webcenter11.1.1.8, Created a domain , pointed to the DR database , all the Data sources names are same in Prod and DR
Doing the configuration  of credentials to communicate with the SOA  and IPM from EM, In DR  it was not populated whatever in the production
Try to created the new credentials and telling already exists in the database, seeing following exception in the database

Caused By: javax.crypto.BadPaddingException: Given final block not properly padded
  at com.sun.crypto.provider.SunJCE_f.b(DashoA13*..)
  at com.sun.crypto.provider.SunJCE_f.b(DashoA13*..)
  at com.sun.crypto.provider.AESCipher.engineDoFinal(DashoA13*..)
  at javax.crypto.Cipher.doFinal(DashoA13*..)
  at oracle.security.jps.internal.keystore.util.CryptoUtil.decrypt(CryptoUtil.java:457)
  at oracle.security.jps.internal.keystore.util.CryptoUtil.decodeAliasWithEncryptedContent(CryptoUtil.java:554)
  at oracle.security.jps.internal.keystore.util.CryptoUtil.decryptPassword(CryptoUtil.java:768)
  at oracle.security.jps.internal.keystore.util.CryptoUtil.decryptPassword(CryptoUtil.java:764)
  at oracle.security.jps.internal.credstore.ldap.CredentialEntityMapper.getEntity(CredentialEntityMapper.java:278)
  at oracle.security.jps.internal.policystore.rdbms.JpsDBDataManager.queryBaseEntities(JpsDBDataManager.java:5032)
  at oracle.security.jps.internal.credstore.ldap.CsfStoreManager.getCredential(CsfStoreManager.java:695)
  at oracle.security.jps.internal.credstore.ldap.CsfStoreManager.getCredential(CsfStoreManager.java:682)
  at oracle.security.jps.internal.credstore.ldap.LdapCredentialStore.getCredential(LdapCredentialStore.java:327)
  at oracle.security.jps.internal.credstore.CredentialMapImpl.containsKey(CredentialMapImpl.java:221)
  at oracle.odc.workspacemanager.WorkspaceManagerSessionBean.loadCredentialMap(WorkspaceManagerSessionBean.java:1897)
  at sun.reflect.GeneratedMethodAccessor394.invoke(Unknown Source)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  at java.lang.reflect.Method.invoke(Method.java:597)
  at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
  at com.oracle.pitchfork.intercept.MethodInvocationInvocationContext.proceed(MethodInvocationInvocationContext.java:103)

 

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


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