Uploaded image for project: 'WildFly Elytron'
  1. WildFly Elytron
  2. ELY-2886

Authentication results in an HTTP 500 if account is locked in EAP 8

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Major Major
    • None
    • None
    • None
    • None
    • Won't do, since Oracle Internet Directory should send LDAP 49 instead LDAP 53 Error Code.

      Getting HTTP 500 when the user is lock on Oracle Internet Directory, when should be 401 Unautorized 

      Caused by: javax.naming.OperationNotSupportedException: [LDAP: error code 53 - Password Policy Error :9001: GSL_ACCOUNTLOCKED_EXCP : Your account is locked. Contact your OID administrator.]
	at java.naming/com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3333)
	at java.naming/com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:3206)
	at java.naming/com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2992)
	at java.naming/com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2906)
	at java.naming/com.sun.jndi.ldap.LdapCtx.ensureOpen(LdapCtx.java:2798)
	at java.naming/com.sun.jndi.ldap.LdapCtx.ensureOpen(LdapCtx.java:2771)
	at java.naming/com.sun.jndi.ldap.LdapCtx.reconnect(LdapCtx.java:2699)
	at org.wildfly.security.elytron-base@2.2.6.Final-redhat-00001//org.wildfly.security.auth.realm.ldap.DelegatingLdapContext.reconnect(DelegatingLdapContext.java:185)
	at org.wildfly.security.elytron-base@2.2.6.Final-redhat-00001//org.wildfly.security.auth.realm.ldap.DirectEvidenceVerifier$1.verifyEvidence(DirectEvidenceVerifier.java:97)
	... 51 more

              rhn-support-pesilva Pedro Silva
              rhn-support-pesilva Pedro Silva
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: