Uploaded image for project: 'PUBLIC - Liferay Portal Community Edition'
  1. PUBLIC - Liferay Portal Community Edition
  2. LPS-74223

Error messages are never displayed to the user in the UI if a callable throws an exception

    Details

      Description

      Description
      An error message will never be displayed to the user if a callable throws an exception because we suppress the exception and just log the error in the console instead. This can cause problems for some use cases.

      For instance, if the user tries to update their password in LDAP, but the updated password fails to be exported to LDAP properly, they will not receive an error message notifying them of this. They will think that their password updated successfully, which can cause them great confusion the next time they try to log in.

      Steps to Reproduce

      1. Start up Liferay and log in as the admin user
      2. Configure Liferay to connect to LDAP
      3. Enable user export and use LDAP password policy
      4. Set up a password policy on the LDAP server
      5. Log in as the new user and attempt to change the new user's password to something that does not meet LDAP's password policy.

      Expected Result: An error message is thrown in the UI to indicate that something went wrong with the user's password change operation.
      Actual Result: No error message appears in the UI. An error with a stack trace appears in the console, but this is not helpful to a user who does not have access to the console.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                minhchau.dang Minhchau Dang
                Reporter:
                michael.bowerman Michael Bowerman (Inactive)
                Participants of an Issue:
                Recent user:
                Michael Saechang
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Days since last comment:
                  1 year, 35 weeks, 3 days ago