My Oracle Support Banner

obPasswordExpiryDate gets Time in Timestamp Truncated to XXXX-XX-XXT00:00:00Z usr_pwd_expire_date gets wrong date on running SSO reconciliation (Doc ID 2725685.1)

Last updated on MAY 01, 2023

Applies to:

Identity Manager - Version and later
Information in this document applies to any platform.


In an OAM/OIM integration environment a password policy is defined in OIM with a password expiry of 120 days:



On user creation



the user gets as expected his/her usr_pwd_expire_date column in the USR table set with the full timestamp of the creation date + 120 days




however the user in LDAP gets his/her attribute obPasswordExpiryDate timestamp with the time truncated always to 00:00:00Z



Now on running SSO reconciliation 



we bring into OIM the incorrect date that then gets converted to the OIM timezone making use loose one day






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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.