Details
-
Bug
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Done
-
None
-
None
-
None
-
Prokopovych - Sprint 145, Prokopovych - Sprint 146, Prokopovych - Sprint 147, Prokopovych - Sprint 148, Prokopovych - Sprint 149
-
Prokopovych
-
Nolana (R3 2022)
-
Spokane Public Libraries, TAMU
-
TBD
Description
Overview:
Using the Users app, you can create a record with an invalid date, wreaking all sorts of havoc.
Steps to Reproduce:
On folio-snapshot, create a user with the birth date 0000-01-01 (yes, seems unlikely, but we've seen it happen twice in a production system, obviously user error).
Expected Results:
User is created with birth date 0000-01-01
Actual Results:
An error is returned indicating that the user cannot be created, BUT the user is actually created, with the value +0000-01-01T00:00:00.000+00:00 in the personal.dateOfBirth property. The user cannot be edited, pulled up in the UI, or retrieved via API. The API returns this error when you try to retrieve the record:
Cannot deserialize value of type `java.util.Date` from String \"+0000-01-11T00:00:00.000+00:00\": not a valid representation (error: Failed to parse Date value '+0000-06-11T00:00:00.000+00:00': Cannot parse date \"+0000-06-11T00:00:00.000+00:00\": not compatible with any of standard forms (\"yyyy-MM-dd'T'HH:mm:ss.SSSX\", \"yyyy-MM-dd'T'HH:mm:ss.SSS\", \"EEE, dd MMM yyyy HH:mm:ss zzz\", \"yyyy-MM-dd\"))
Additional Information:
As a side effect, the /users/expire/timer API will be broken if this user ever expires, as the module will be unable to process the retrieved user record for the same reason and will log an NPE and the connection will hang open until eventually mod-users has 1000 connections open to Okapi and no more can be opened, effectively crashing the system.
Interested parties:
ggoldner
TestRail: Results
Attachments
Issue Links
- defines
-
UXPROD-3691 R3 2022 | Prokopovych Enhancements/Bugfixes/NFR/tech debt
-
- Closed
-
- relates to
-
MODUSERS-320 User with invalid date value will break /users/expire/timer API
-
- Closed
-