Return-Path: X-Original-To: apmail-directory-dev-archive@www.apache.org Delivered-To: apmail-directory-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C49B11068D for ; Mon, 24 Feb 2014 16:15:21 +0000 (UTC) Received: (qmail 41736 invoked by uid 500); 24 Feb 2014 16:15:21 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 41708 invoked by uid 500); 24 Feb 2014 16:15:20 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 41698 invoked by uid 99); 24 Feb 2014 16:15:20 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Feb 2014 16:15:20 +0000 Date: Mon, 24 Feb 2014 16:15:20 +0000 (UTC) From: "Kiran Ayyagari (JIRA)" To: dev@directory.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (DIRSERVER-1676) Provide a set of error codes along with an AuthenticationException to indicate its root cause. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DIRSERVER-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kiran Ayyagari resolved DIRSERVER-1676. --------------------------------------- Resolution: Fixed Assignee: Kiran Ayyagari Thanks for confirming, and I totally forgot about the ppolicy enum, that is the way to compare. > Provide a set of error codes along with an AuthenticationException to indicate its root cause. > ---------------------------------------------------------------------------------------------- > > Key: DIRSERVER-1676 > URL: https://issues.apache.org/jira/browse/DIRSERVER-1676 > Project: Directory ApacheDS > Issue Type: Improvement > Components: core > Affects Versions: 2.0.0-M4 > Environment: 64bit Windows, using 32 bit jvm to support wrapper.dll > Reporter: Carlo Accorsi > Assignee: Kiran Ayyagari > Priority: Minor > Labels: apacheds > Fix For: 2.0.0-M16 > > > There may be more cases to consider but when a user supplies an incorrect password or the account is locked, > a javax.naming.AuthenticationException is thrown. Currently comparing the strings returned by ex.getMessage() is > the only way to determine which event occurred. > [LDAP: error code 49 - INVALID_CREDENTIALS: Bind failed: ERR_229 Cannot authenticate user uid=xyz,o=corp] > [LDAP: error code 49 - INVALID_CREDENTIALS: Bind failed: account was permanently locked] -- This message was sent by Atlassian JIRA (v6.1.5#6160)