My Oracle Support Banner

OAM Pre-Authentication Rule Not Working For Webgate Protected Applications (Doc ID 2388292.1)

Last updated on APRIL 18, 2018

Applies to:

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

Symptoms

On : 11.1.2.3.170117 version, Authentication Engine

ACTUAL BEHAVIOR
---------------
1. Customer has pre-authentication rule condition set to request.userAgent.lower().find('firefox') > 0 or str(request.requestMap['User-agent']).lower().find('firefox') .
2. It does not switch authentication scheme as expected.
3. Even 'TRUE' == 'TRUE' is not working.
4. The rule works for SAML2 based application. It is not working for webgate protected application.

EXPECTED BEHAVIOR
-----------------------
1. When webgate protected application using pre-authentication rule is accessed, it is expected to redirect to new authentication scheme.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Access webgate protected application that is using not working application domain, pre-authentication rule.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Users are not able to authenticate as expected.

Changes

 

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!


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