My Oracle Support Banner

EPOC Data Format is not Capturing the Right Value (Doc ID 1183204.1)

Last updated on MARCH 08, 2017

Applies to:

COREid Identity - Version: 10.1.4.2 and later   [Release: 10g and later ]
Information in this document applies to any platform.

Symptoms

The EPOC data format is not capturing the right Value.

Steps to reproduce
1. Log into a protected resource
2. Query LDAP attribute lastsucessfullogin returns the epoch format...1276832167
3. Call http://www.esqsoft.com/javascript_examples/date-to-epoch.htm
4. Enter the epoch time from step 1 and select convert, returns...

Thu Jun 17 2010 20:36:07 GMT-0700 (Pacific Daylight Time)

5. The time on the access server shows 12:36 PM
6.Based on this same URL.....http://www.esqsoft.com/javascript_examples/date-to-epoch.htm
enter the date...June 17 2010 and the time 12:36
then select epoch...it returns...

1276805123

The EPOC data formats should be the same, but are not.

Cause

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
  Symptoms
  Cause
  Solution
  References

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.

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