LDAP Authentication/Listener and LDAP Scheduled Load Imports Using the Same Transform Map are Showing Different Timezone DatesIssue When a user authenticates with LDAP Authentication or the LDAP Listener updates a user record and the transform runs for date fields, the dates will be set to the system's default timezone. When the LDAP Scheduled Load runs which uses the same transform map as the authentication/listener updates, the date fields will be set using a different timezone.ReleaseApplies to any release.CauseThe LDAP Authentication/LDAP listener updates are dependent on the system's default timezone as set at: System Properties -> System -> "System timezone for all users unless overridden in the user's record". The LDAP Scheduled Loads job has the "Run as" set to a user that is in a different timezone (that user's "Time zone" setting in their sys_user record) than the system's default timezone OR the "Run as tz" is set set to a different timezone than the system's default timezone. ResolutionTo be sure the LDAP Scheduled Loads job dates match that of the LDAP Authentication/LDAP Listener dates be sure that the "Run as tz" setting in the LDAP Scheduled Loads job is set to the appropriate timezone value to match the system's default time as set at: System Properties -> System -> "System timezone for all users unless overridden in the user's record".