My Oracle Support Banner

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

Last updated on AUGUST 09, 2018

Applies to:

Oracle Business Process Management Suite - Version and later
Oracle SOA Suite - Version and later
Information in this document applies to any platform.


When trying to login to BPM Composer or the BPM Workspace you may experience an error when using the sAMAccountName or any other attribute than 'cn' configured in the weblogic identity provider.

The problem will occur when the identity provider uses any id field other than cn as user ID (For example, sAMAccountName or uid). The following exception will show up in the SOA server diagnostic 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 you should notice that the cn attribute of the user is being used, rather than whatever attribute you configured in the identity provider.




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.