1. error code 53
===========================================================================
Question: data backend exception occurs when you create a new user
In WebSphere Portal Express, you can set the minimum and maximum length of the password. If the policy password length and LDAP server settings are not the same, when you create a user, you may see the following exception:
EJPSG0015E: Data Backend Problem com.ibm.websphere.wmm.exception.WMMSystemException:
The following Naming Exception occurred during processing:
"javax.naming.OperationNotSupportedException: [LDAP: error code 53 - 0000052D:
SvcErr: DSID-031A0FBC, problem 5003 (WILL_NOT_PERFORM), data 0
]; remaining name 'cn=see1anna,cn=users,dc=wps510,dc=rtp,dc=raleigh,dc=ibm,dc=com';
resolved object com.sun.jndi.ldap.LdapCtx@7075b1b4".
Reason: This is due to the "password can not meet the requirements of the password policy" led to
solution:
1. Open the Domain Security Policy - Security Settings - Account Strategy - password policy - Passwords must meet complexity requirements. Define this policy setting is: Disabled. / Minimum password length: Define this policy is set to 0.
2. Open the Domain Controller Security Policy - Security Settings - Account Strategy - password policy - Passwords must meet complexity requirements. Define this policy setting is: Disabled. / Minimum password length: Define this policy is set to 0.
3. Finally, run the Group Policy refresh command: gpupdate / force
===========================================================================
2. Need to specify class name
===========================================================================
javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial
Cause: LdapContext in the last link is processed close (), LdapContext = null;
Solution: Do not close;
3. error code 50
===========================================================================
javax.naming.NoPermissionException: [LDAP: error code 50 - 00002098: SecErr: DSID-03150A45, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0
4. error code 68
===========================================================================
javax.naming.NameAlreadyBoundException: [LDAP: error code 68 - 00000524: UpdErr: DSID-031A0F4F, problem 6005 (ENTRY_EXISTS), data 0
The reason: the user to create already exists
7. No trusted certificate
===========================================================================
javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: No trusted certificate found
1.cas machine A, the A a, b, c service works well
B is located 2.website machine, CAS can intercept requests jump javax.net.ssl.SSLHandshakeException
A green generated on the client key, introduced into B
A run
sudo keytool -genkey -alias tomcat -keyalg RSA -keypass changeit -storepass changeit -keystore server.keystore -validity 3600
$ keytool -export -trustcacerts -alias tomcat -file server.cer -keystore server.keystore -storepass changeit
$ sudo keytool -import -trustcacerts -alias tomcat -file server.cer -keystore $JAVA_HOME/jre/lib/security/cacerts -storepass changeit
B run to the last sentence
Building trust, customer, service keys, multiple customers
8. error code 1
===========================================================================
javax.naming.NamingException: [LDAP: error code 1 - 00000000: LdapErr: DSID-0C090AE2, comment: In order to perform this operation a successful bind must be completed on the connection., data 0, vece
The reason: the new domain user when, ctx is not bound administrator user
Solution: ctx.addToEnvironment (Context.SECURITY_PRINCIPAL, adminUser + "@" + ldapProperty.getDomain ());
ctx.addToEnvironment(Context.SECURITY_CREDENTIALS, adminPwd);
9. error code 50
==========================================================================
javax.naming.NoPermissionException: [LDAP: error code 50 - 00000005: SecErr: DSID-03151E04, problem 4003 (INSUFF_ACCESS_RIGHTS)
The reason: the new domain user time, ctx bound to an ordinary user (the user does not have permission to new users)
Workaround: Use the administrator user to bind:
ctx.addToEnvironment(Context.SECURITY_PRINCIPAL, adminUser + "@" + ldapProperty.getDomain());
ctx.addToEnvironment(Context.SECURITY_CREDENTIALS, adminPwd);
10. error code 19
==========================================================================
javax.naming.directory.InvalidAttributeValueException: [LDAP: error code 19 - 0000052D: AtrErr: DSID-03190F00, #1:
0: 0000052D: DSID-03190F00, problem 1005 (CONSTRAINT_ATT_TYPE)
The reason: the most likely does not meet the Domain Security Policy: If password complexity, minimum password age, enforce password history. That length, characters included how long can modify your password, whether you can use a password history and so on.
11. LDAP: error code 50
==========================================================================
javax.naming.NoPermissionException: [LDAP: error code 50 - 00000005: SecErr: DSID-031A0F44, problem 4003 (INSUFF_ACCESS_RIGHTS)
The reason: This is the original replace operation code used in this AD in the corresponding password is reset (normal users by default do not have this privilege, the administrator can operate), another old password you provided when an error operation may remove this anomaly report
12. RSA premaster secret error
==========================================================================
javax.naming.CommunicationException: simple bind failed: 172.18.20.4:636 [Root exception is javax.net.ssl.SSLKeyException: RSA premaster secret error]
The reason: JDK JDK and Tomcat configuration to add the certificate does not match. Such as: a certificate storage path C: /Java/jdk1.6.0_10/jre/lib/cacerts Tomcat is configured to JDK C: time / Java / jre6, such that the two paths are inconsistent, the SSL authentication, the certificate can not be found
13.No trusted certificate found
==========================================================================
javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: No trusted certificate found
The reason: Trust Certificate Store file path is incorrect
Solution: correct project / WEB-INF / classes directory
14. error code 49
==========================================================================
javax.naming.AuthenticationException: [LDAP: error code 49 - 80090308: LdapErr: DSID-0C090334, comment: AcceptSecurityContext error, data 52e, vece
Cause: The user name or password is incorrect
