Session: Time Unit Condition Uses A Wrong Time Format (Doc ID 2300001.1)

Last updated on AUGUST 24, 2017

Applies to:

Oracle Adaptive Access Manager - Version 11.1.2.3.0 and later
Information in this document applies to any platform.

Goal

If we use the Session: Time Unit condition type, the rule seems to get triggered for PM values when you specify them in 12 hours format. For example, the rule will never get triggered if you specify the condition using 20, 21, but it will get triggered if you specify it as 8, 9. In the second case, it will get triggered both if you test it between 8AM-9AM or if you test it between 8PM-9PM.

Solution

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