-
Suggestion
-
Resolution: Won't Do
-
None
-
None
-
5
-
NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.
Currently, Confluence does not handle the LDAP error message related to Password Policy set from external directory, just throwing the original LDAP error on the Confluence log file:
com.atlassian.crowd.exception.runtime.OperationFailedException: org.springframework.ldap.OperationNotSupportedException: [LDAP: error code 53 - 00002035: LdapErr: DSID-0C090A36, comment: Operation not allowed through GC port, data 0, vece]; nested exception is javax.naming.OperationNotSupportedException: [LDAP: error code 53 - 00002035: LdapErr: DSID-0C090A36, comment: Operation not allowed through GC port, data 0, vece]; remaining name 'cn=xxxx,ou=xxxx,ou=xxxxx,dc=xxxxxx,dc=xxxxx'
at com.atlassian.crowd.embedded.core.CrowdServiceImpl.updateUserCredential(CrowdServiceImpl.java:384)
or:
2016-03-08 08:50:31,675 ERROR [ajp-bio-8016-exec-1] [atlassian.confluence.servlet.ConfluenceServletDispatcher] sendError Could not execute action
-- referer: https://dealflow.aramcoventures.com/confluence/resetuserpassword.action?username=mark.rosa&token=32677d2b6bf107c0acad295ba2de35945f12194d | url: /confluence/doresetuserpassword.action | userName: anonymous
com.atlassian.crowd.exception.runtime.OperationFailedException: org.springframework.ldap.OperationNotSupportedException: [LDAP: error code 53 - 0000052D: SvcErr: DSID-031A12D2, problem 5003 (WILL_NOT_PERFORM), data 0
It would be great if Confluence could handle it and warn its users that the password does not match the Policy.
- is related to
-
- Gathering Interest
-
- Under Consideration
- relates to
-
- Closed
-
- Gathering Interest
- mentioned in
![[Atlassian Documentation] Page](https://confluence.atlassian.com/images/icons/favicon.png "[Atlassian Documentation] Page"){kind=icon}
[CONFSERVER-34742] Confluence to recognize LDAP Password Policy
Saul Perdomo
added a comment - Hi Devs,
I'm the client who reported this issue (Ref CSP-129810).
I'd like to clarify that the application crashes with an error dump that is very visible to the user – it doesn't only show up in logs.
As a software company ourselves, we call any issue that a) can be reproduced, b) is due to improper error handling, and c) generates a very loud, very user-unfriendly "System Error" page, a bug. A *high-severity* bug, actually.
What is the process to upgrade this ticket from "Improvement" to a "Bug"?
P.S. I am attaching a screenshot of what the end-user sees after a run-of-the-mill unsuccessful password change attempt.
Saul Perdomo
added a comment - Hi Devs,
I'm the client who reported this issue (Ref CSP-129810).
I'd like to clarify that the application crashes with an error dump that is very visible to the user – it doesn't only show up in logs.
As a software company ourselves, we call any issue that a) can be reproduced, b) is due to improper error handling, and c) generates a very loud, very user-unfriendly "System Error" page, a bug . A * high-severity * bug, actually.
What is the process to upgrade this ticket from "Improvement" to a "Bug"?
P.S. I am attaching a screenshot of what the end-user sees after a run-of-the-mill unsuccessful password change attempt.
Thank you for raising this suggestion.
We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Sometimes potentially valuable tickets do get closed where the Summary or Description has not caught the attention of the community. If you feel that this suggestion is valuable, consider describing in more detail or outlining how this request will help you achieve your goals. We may then be able to provide better guidance.
For more context, check out our Community blog on our updated workflow for Suggestions
Cheers,
Confluence Product Management