My Oracle Support Banner

How to use sAMAccountName, uid, mail or other attributes as the principal name in BPM 12.2.1.x? (Doc ID 2164746.1)

Last updated on NOVEMBER 13, 2022

Applies to:

Oracle Business Process Management Suite - Version and later
Oracle SOA Suite - Version and later
Oracle WebCenter Content: Imaging - Version to [Release 12c]
Information in this document applies to any platform.


When trying to login to BPM Composer, BPM Workspace, and other applications an error will occur when using the sAMAccountName, uid, or any other attribute other than 'cn' setup as the principal name in the weblogic provider configuration.  The following exception will show up in the server logs when trying to login:

User not found.
User "user" is not found in configuration ""
Check if the user exists in the repository specified by the configurations. Check the error stack and fix the cause of the error.


In the error the cn attribute of the user will be shown rather than whatever other attribute is configured in the identity provider in the weblogic console.


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
 Configuration for Active Directory (sAMAccountName) as Identity Provider
 Configuration for uid using Oracle Directory Server Enterprise Edition (ODSEE), OUD, or iPlanet as Identity Provider
 How to use the mail attribute as the principal id?
 Additional details for
 Additional details on versions earlier than

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