[jira] Updated: (DIRSERVER-640) bring error hints from
Web Server forum
Back To The Forum Home!Search!Private Messaging System

Web Server Talk Web Server Talk > Web Servers reviews > Apache Server configuration support > Apache Directory Project > [jira] Updated: (DIRSERVER-640) bring error hints from




  Last Thread   Next Thread Next
  Show Printable Version Email this Page Subscribe to this Thread      Post New Thread    Post A Reply      

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


View Ip Address Report This Message To A Moderator Edit/Delete Message


 
06-18-06 12:11 AM

[ 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 AbstractAuthenticato
r 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 AbstractA
uthenticator.
> If the authentication fails I use LdapAuthenticationException or LdapNoPer
missionException and I appreciate a lot to be able to provide some hint (Str
ing 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]) inva
lidCredentials
>             Matched DN : 'null'
>             Error message : 'Bind failed'>>
> It appears that the culprit is org.apache.directory.server.core.authn.Auth
enticationService.bind(NextInterceptor next, Name bindDn, byte[] credent
ials, 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 mo
re 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







[ Post a follow-up to this message ]



    Sponsored Links  




 





   All times are GMT. The time now is 12:42 PM.      Post New Thread    Post A Reply      
  Last Thread   Next Thread Next


Most Popular forums 

Forum Jump:
Rate This Thread:

Forum Rules:
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is OFF
vB code is ON
Smilies are ON
[IMG] code is OFF
 
Medical and Health forum | Computer Games Reviews | Graphics design forum

Back To The Top
Home | Usercp | Faq | Register