Oracle Identity Manager (OIM) Open Tasks Form Interprets Four Digit Years to Two Digits Resulting in Potential Corruption or Validation Errors
(Doc ID 2817587.1)
Last updated on NOVEMBER 05, 2021
Applies to:Identity Manager - Version 22.214.171.124.201011 and later
Information in this document applies to any platform.
When a task is sent to a target resource, and that resource is unavailable, the task is recorded in 'Open Tasks' where it can be reviewed, edited, or resubmitted. If the account data (resource form) contains dates, those dates
are rendered in the UI based on a two digit year. If those last two digits are less than or equal to '49', then the year is converted to 20xx. If the last two digits are greater than '49', then the year is interpreted as 19xx. If the user commits changes to the form, the date values are overridden with these altered four digit years.
So, for example, if the provided date is 12/31/9999, the form displays the date as 12/31/99 and alters the date in the form field to 12/31/1999.
Basically, if the last two digits of the year are greater than '49', the first two digits become '19'. If those last two digits are less than or equal to '49', then the year is prefixed with '20' instead. This can result in years converting from 9999 to 1999, and 1940 appearing as 2040.
The bigger problem is that some target resources (SAP in this case) require a thru-date for the account, and the customer consistently provides 12/31/9999. The form will edit the date to 12/31/1999. A form level validation will compare the start and thru-dates, and when the thru-date is less than the start date, it raises an error. So in that case, the form cannot proceed because the preferred thru-date is considered before the start date.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document