The Drift Field For The Validate Timestamp Filter Behaves Different In OAG and OEG

(Doc ID 2013969.1)

Last updated on SEPTEMBER 21, 2017

Applies to:

Oracle API Gateway - Version 11.1.2 to 11.1.2 [Release 11gR2]
Information in this document applies to any platform.


 In OAG, when using  "Validate Timestamp"  filter and facing the below issues:

1. In OAG, at the Filter level (in Policy Studio) maximum value can be set to 5000 seconds.
    If set to 5000000 seconds at the filter level in Policy Studio, it automatically sets back to 5000 as soon as you open the policy/filter again, in Policy Studio.
2. In OEG, if 5000 seconds is set, it is converted to 5000000 milliseconds but in OAG it remains as 5000. That is no conversion from
  seconds to milliseconds in OAG. Is this expected behavior ?


As shown this behavior is not happening in OEG


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms