Apache Directory Project - [jira] Updated: (DIRSERVER-640) bring error hints from

This is Interesting: Free IT Magazines  
Home > Archive > Apache Directory Project > June 2006 > [jira] Updated: (DIRSERVER-640) bring error hints from





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author [jira] Updated: (DIRSERVER-640) bring error hints from
Ralf Hauser (JIRA)

2006-06-17, 7:11 pm

[ http://issues.apache.org/jira/brows...ER-640?page=all ]

Ralf Hauser updated DIRSERVER-640:
----------------------------------

Attachment: AuthenticationService.java.patch

see also DIRSERVER-649

> bring error hints from CustomAuthenticators extending AbstractAuthenticator back to the client.
> -----------------------------------------------------------------------------------------------
>
> Key: DIRSERVER-640
> URL: http://issues.apache.org/jira/browse/DIRSERVER-640
> Project: Directory ApacheDS
> Type: Improvement


> Components: ldap
> Versions: 1.0-RC3
> Environment: windows/linux
> Reporter: Ralf Hauser
> Attachments: AuthenticationService.java.patch
>
> For the authentication, I use a CustomAuthenticator that extends AbstractAuthenticator.
> If the authentication fails I use LdapAuthenticationException or LdapNoPermissionException and I appreciate a lot to be able to provide some hint (String explanation) why the exception was thrown.
> Unfortunately, this hint never reaches the client. I only sees "error code 49 - Bind failed" - the equivalent is visible in the server log as
> <<Ldap Result
> Result code : (ResultCodeEnum[INVALIDCREDENTIALS=49]) invalidCredentials
> Matched DN : 'null'
> Error message : 'Bind failed'>>
> It appears that the culprit is org.apache.directory.server.core.authn.AuthenticationService.bind(NextInterceptor next, Name bindDn, byte[] credentials, List mechanisms, String saslAuthId) throws NamingException
> where that expception is caught, neither its class is analyzed in detail nor is there any attempt to use "explanations" when re-throwing even though an LdapAuthenticationException constructor does exist that takes a "msg" for explanations.
> Therefore my suggestion: please make sure that it is possible to provide a user more information by optionally appending an "explantion" to the 'Bind failed' a client currently sees in an ldap client.


--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secur...nistrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira


Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com