cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "sadhu suresh (JIRA)" <>
Subject [jira] [Reopened] (CLOUDSTACK-1172) Ldap enhancements
Date Thu, 01 Aug 2013 17:37:49 GMT


sadhu suresh reopened CLOUDSTACK-1172:

Now we are showing the response with ldap exception details but not sowing exact reason for
failure.again end user has to look for ldap error codes and confirm.

It will good if some exception will be identified and mapped properly

like for invalid password,right now  we are showing:

{ "ldapconfigresponse" : {"uuidList":[],"errorcode":431,"cserrorcode":4350,"errortext":"Naming
Exception, check you ldap data ! [LDAP: error code 49 - 80090308: LdapErr: DSID-0C090334,
comment: AcceptSecurityContext error, data 52e, vece´┐Ż]"} }

But 52 e refer to invalid credentials so if we mapp and display proper error message for the
corresponding error codes will be  good

The AD-specific error code is the one after "data" and before "vece" or "v893" in the actual
error string returned to the binding process

525 	user not found
52e 	invalid credentials
530 	not permitted to logon at this time
531 	not permitted to logon at this workstation
532 	password expired
533 	account disabled
701 	account expired
773 	user must reset password
775 	user account locked

> Ldap enhancements
> -----------------
>                 Key: CLOUDSTACK-1172
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.0.1
>            Reporter: sadhu suresh
>            Assignee: Abhinandan Prateek
>            Priority: Minor
>             Fix For: 4.2.0
> Right now we are not logging proper error message in the logs when any failure occur
due to invalid credentials or for any other reason.
> It will be good if we provide proper message for failure cases so that it will be easy
 for  the end to identify the root cause of problem.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message