-
Title
When using the CLI / API methods to Add a Password Request using the 'ForUserName' option, dates are not calculated from the correct TPAM User. -
Description
If the CLI or API calls are made (such as CLI AddPwdRequest) and the 'ForUserName' variable is used, the date calculations will not calculate correctly. This may cause the request to fail with the message "Release Date cannot be a past date" even though the date/time is valid for the user entered via the 'ForUserName' flag.
The same issue exists for the Session Request (such as the CLI AddSessionRequest)
The expected behavior from the documentation: "If the --ForUserName is assigned to a time zone other then UTC, this value represents the local time for the user."
-
Cause
The date is not calculated correctly against the user entered via the 'ForUserName' flag. For example, if the time is 11am Eastern and the request is created for 11:15am Eastern, this may fail as this time is 'expired' when calculated against UTC. -
Resolution
WORKAROUND: As the timezone is not calculated correctly to consider the TPAM user's timezone when using the 'ForUserName' flag, perform date calculations accordingly, external to TPAM.
STATUS: This issue has been addressed in TPAM 2.5.920 via BFER 9673. From the 2.5.920 Release Notes under "Resolved Issues":
"CLI command AddPwdRequest with --ForUserName parameter is not using the time zone of the --ForUserName for the request times."
-
Change Request
9673