Details
-
Bug
-
Resolution: Fixed
-
Medium
-
None
Description
JIRA should better handle errors return from Crowd. For example, if Crowd doesn't allow user to reuse they old password and user will try to do so, JIRA doesn't display any notification, but the error:
Cause: com.opensymphony.user.ImmutableException Stack Trace: [hide] com.opensymphony.user.ImmutableException at com.opensymphony.user.User.setPassword(User.java:106) at com.atlassian.jira.web.action.user.ChangePassword.doExecute(ChangePassword.java:36) at webwork.action.ActionSupport.execute(ActionSupport.java:153) at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:54) at webwork.dispatcher.GenericDispatcher.executeAction(GenericDispatcher.java:132) at com.atlassian.jira.web.dispatcher.JiraServletDispatcher.service(JiraServletDispatcher.java:209)
and in the log file is recoded:
2007-10-03 13:47:54,999 http-8443-Processor19 ERROR [crowd.integration.osuser.CrowdCredentialsProvider] Password already has been used. com.atlassian.crowd.integration.exception.InvalidCredentialException: Password already has been used. at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
It would be nice, if JIRA would return something more meaningful to the end-users.
Attachments
Issue Links
- is duplicated by
-
JRASERVER-16255 Forgot Password/Crowd Integration exception handling and regex improvements
- Closed
- relates to
-
CWD-1206 Throw IllegalArgumentException in CrowdCredentialProvider's changePassword to throw a friendlier 500 page exception (JRA-13685)
- Closed
-
JRASERVER-14836 Ensure JIRA behaves correctly when a user who has assigned or reported issues has been deleted
- Gathering Interest