Time Based Pattern Is Not Getting Triggered For Various Special Cases
Last updated on JANUARY 22, 2014
Applies to:Oracle Adaptive Access Manager - Version 188.8.131.52.1 to 184.108.40.206.1 [Release 11gR1 to 11gR2]
Information in this document applies to any platform.
If login time (hour) matches the start time specified in the time range then an alert will not be triggered.
For example if you have defined the time range as start=5 and end=10 then any login attempts made between 5am to 5:59am do not trigger alerts.
In this scenario the alerts are triggered for logins made between 6am and 10am.
If login time is between 11pm to 12am then bucket for 23..24 does not get created when timerange pattern has bucket size (increment property) set to 1.
The first login that matches the pattern bucket will not trigger the alert.
For example if you have defined a new time range as start=2 and end=8 then you expect that any logins done between 2am and 8am will trigger a alert, but the first login does not trigger the alert. However, each subsequent login does.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms