My Oracle Support Banner

OAM 11g R2 WNA Not Working When Principal Name Parameter Is Not Using FQDN Error User account is locked. Authentication failed (Doc ID 1507592.1)

Last updated on OCTOBER 24, 2018

Applies to:

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

Symptoms

On : OAM 11.1.2.0.0 version, Configuration Service

Background
----------------
Windows Native Authentication (WNA) integration with Oracle Access Manager  (OAM) 11gR2

Environment
----------------
- OAM 11.1.2
- Windows Server 2008 R2 Standard Service Pack 2 as the Active Directory (AD) server
- This is a dual domain in a forest. Domain functional level is Windows Server 2008. Forest Functional level is Windows Server 2003.


ACTUAL BEHAVIOR
--------------------------
OAM 11g R2 WNA not working and fail with below error:

[2012-11-19T10:17:25.131+11:00] [oam_server1] [ERROR] [OAM-02010] [oracle.oam.controller] [tid: [ACTIVE].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: ] [ecid: 6654268942fbb7c3:23268570:13b15c4dda7:-8000-0000000000000256,0] [APP: oam_server#11.1.2.0.0] User account is locked. Authentication failed.

 

EXPECTED BEHAVIOR
-----------------------
Integration with WNA should work without prompt for login after user authenticated to Windows Desktop.

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


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