My Oracle Support Banner

Authentication to OIM using Active Directory (AD) credentials fails (Doc ID 1387837.1)

Last updated on NOVEMBER 01, 2022

Applies to:

Identity Manager - Version and later
Information in this document applies to any platform.


1. The user can login to WebLogic using the AD password
2. At the same time the user sees the 403 error if logging into OIM using the AD password but can login using the OIM password.

The log contains the following

[2011-12-05T09:33:48.831-06:00] [SERVERNAME] [ERROR] [] [OIM Authentication Provider] [tid: [ACTIVE].ExecuteThread:TID for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: ECID] [APP: oim#] oracle.iam.platform.auth.providers.wls.OIMSignatureLoginModule login() Invalid Input username/password

Other errors in the log

<Dec 12, 2011 8:23:36 AM CST> <Error> <OIM Authentication Provider> <BEA-000000>

<oracle.iam.platform.auth.providers.wls.OIMSignatureLoginModule login() Invalid Input username/password>
<Dec 12, 2011 8:23:48 AM CST> <Error> <OIM Authenticator> <BEA-000000> <User USERNAME not found>
<Dec 12, 2011 8:23:58 AM CST> <Error> <OIM Authentication Provider> <BEA-000000> [Security:090294]could not get connection

'weblogic.kernel.Default (self-tuning)' has been busy for "621" seconds working on the request

"weblogic.kernel.WorkManagerWrapper$1@SESSION_ID", which is more than the configured time (StuckThreadMaxTime) of "600"

seconds. Stack trace:
Thread-15 "[STUCK] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'" <alive, in native,

suspended, priority=1, DAEMON> {


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

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