#993 Inconsistent getUser() result handling
Closed: migrated 3 years ago by dmoluguw. Opened 9 years ago by edewata.

Currently the UGSubsystem.getUser() returns a null value if the user is not found or if an error occurs. In many cases the code calling getUser() is not handling the result properly.

Ideally it should work like this:

  • getUser() should return a null only if the user doesn't exist.
  • getUser() should throw an exception if there is other error.
  • The caller should check whether the return value is null, and handle each case properly.
  • The caller should either catch the exception and handle it properly, or rethrow the exception. The caller should not just catch and ignore the exception.

Proposed milestone: 10.3

Per CS/DS meeting of 5/5/2014, moving to milestone 10.3.

Metadata Update from @edewata:
- Issue set to the milestone: UNTRIAGED

7 years ago

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/1559

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Metadata Update from @dmoluguw:
- Issue close_status updated to: migrated
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata