Nds Error 669
Contents |
login, password, time and address restrictions are set fact Novell eDirectory 8.5 for NetWare 5.1 DS.NLM version 85.12A or above LDAP Error: "49" LDAP Error: "53" NDS Error: "login lockout ldap error code 49 - nds error failed authentication (-669) -197" NDS Error: "maximum logins exceeded or Q stn not server -217" NDS nds error login lockout (-197) Error: "bad login time or Q halted -218" NDS Error: "log account expired -220" NDS Error: "bad password -222" NDS ldap error code 53 Error: "password expired -223" NDS Error: "failed authentication -669" fix The LDAP bind operation initiates a protocol session and (optionally) authenticates a user to the server. The authentication process requires that a
Ldap Error 49
user's distinguished name and password be passed as part of the bind. The server will return an LDAPResult upon recieving and processing the bind. The LDAPResult contains three main fields - resultCode, matchedDN and errorMessage. The resultCode contains the LDAP error number; a code of zero is used to indicate successful completion of the operation. In the case of a bind, this would mean that the ldap error code 49 invalid credentials user has authenticated successfully. The matchedDN is not used in the bind operation; it will always be a blank string. The errorMessage is vendor defined. If the bind was not successful, the server can include an additional ASCII text message indicating possible causes of the problem. When NDS password restrictions are set and the authentication fails, the LDAPResult will contain additional information in the errorMessage. In addition, the resultCode could be different than the standard LDAP one indicating an incorrect password. Developers might finds this data helpful in alerting the user to the reason why they couldn't login. For instance, the application could distinguish between a user whose account has been disabled and one who just typed in the wrong password. The following section details the type of NDS password restriction set and the corresponding resultCode and errorMessage when the user can't authenticate. Restriction: None Description: No NDS password restrictions are set. Rather, this details the results when the user has actually typed the wrong password. resultCode: 49 errorMessage: "NDS error: failed authentication (-669)" Restriction: Password expired with grace logins remaining Description: The administrator has set "Force Password Changes" and the user's password has expired. The
STERLINGNFX Technote (troubleshooting) Problem(Abstract) Error when trying to setup LDAP authentication for external account http://stackoverflow.com/questions/1206727/ldap-invalid-credentials-not-loading-authentication-failure-url Symptom No activity on LDAP server when trying to authenticate external account Error Message [2007-10-15 12:23:18.483] DEBUG ldap error 000000000000 GLOBAL_SCOPE SecurityManager user:severs attempting to log in (SSO:false) [2007-10-15 12:23:18.484] DEBUG 000000000000 GLOBAL_SCOPE LDAPAuthentication user:severs is identified as an EXTERNAL GIS User [2007-10-15 12:23:18.484] DEBUG 000000000000 GLOBAL_SCOPE LDAPAuthentication performing LDAP search.... [2007-10-15 12:23:18.558] DEBUG 000000000000 ldap error code GLOBAL_SCOPE LDAPAuthentication ...search filter:(cn=severs) [2007-10-15 12:23:18.558] DEBUG 000000000000 GLOBAL_SCOPE LDAPAuthentication ...selected attributes:userPassword [2007-10-15 12:23:18.558] DEBUG 000000000000 GLOBAL_SCOPE LDAPAuthentication ...search root:o=associates [2007-10-15 12:23:18.694] DEBUG 000000000000 GLOBAL_SCOPE LDAPAuthentication entry found -> cn=SEVERS,o=associates [2007-10-15 12:23:18.694] DEBUG 000000000000 GLOBAL_SCOPE LDAPAuthentication ...binding as user: cn=SEVERS,o=associates [2007-10-15 12:23:18.695] DEBUG 000000000000 GLOBAL_SCOPE LDAPAuthentication ......connection properties: {java.naming.provider.url=ldap://10.1.5.7:389, java.naming.factory.initial=com.sun.jndi.ldap.LdapCtxFactory, java.naming.security.principal=cn=SEVERS,o=associates, java.naming.security.authentication=simple, java.naming.security.credentials=gentran01} [2007-10-15 12:23:21.744] ERROR 000000000000 GLOBAL_SCOPE LDAPAuthentication ......bind as user NAMING EXCEPTION: javax.naming.AuthenticationException: [LDAP: error code 49 - NDS error: failed authentication (-669)] at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3005) at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2951) at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2752) at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2666) at com.sun.jndi.ldap.LdapCtx.
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Ldap invalid credentials not loading authentication failure url up vote 1 down vote favorite Able to do the custom ldap authentication for external db authorities. But when I am trying to test wrong password the authentication failure URL is not showing instead my browser prints the exception details.Below is my securitycontext.xml and exception given: