-
Suggestion
-
Resolution: Answered
-
None
-
None
-
None
Currently, Crowd will display ERROR message returm from AD directly in the UI which is misleading as it does not specify the exact cause of the ERROR which confused the user.
For example, the following ERROR displayed in the UI when the user does not follow the password policies in the AD environment. Refer to LDAP: error code 53 WILL_NOT_PERFORM
org.springframework.ldap.OperationNotSupportedException: [LDAP: error code 53 - 0000001F: SvcErr: DSID-031A120C, problem 5003 (WILL_NOT_PERFORM), data 0
]; nested exception is javax.naming.OperationNotSupportedException: [LDAP: error code 53 - 0000001F: SvcErr: DSID-031A120C, problem 5003 (WILL_NOT_PERFORM), data 0
]; remaining name 'cn=XXXXXXX,cn=users,dc=example,dc=com'
Kindly refer the attached screenshot for more details.
Therefore, it will be much helpful if we could translate the ERROR message to human readable format to avoid confusion.
Thank you for taking the time to file this issue. Feedback like yours helps us release valuable Crowd features that solve problems for the greater customer base. To that end we aim to add features to Crowd that would best fulfill our customers needs. However at this time, this suggestion is not on the Crowd development roadmap and due to that fact we have decided to close your suggestion.
We intentionally decided to put more details into this error message as we do believe that having them here may help to resolve issue quicker as the error may contain LDAP (i.e. AD) specific details. Given the fact that we support different types of LDAP directories it would be hard to detect what kind of issue user is having, based on the error message received from directory, in order to display more user friendly yet helpful message.
We could put here a generic statement like 'There was an error while saving configuration', but we believe this would make the resolution of the problem harder as the user would have to refer to Crowd log files to get more insight into the real issue he or she is having.
If you still feel that this issue is still relevant to your needs, please feel free to raise a new issue and link to this one.
If you would like to see how we select features for a new release, please read http://confluence.atlassian.com/display/DEV/Implementation+of+New+Features+Policy.