Skip to Main Content

Analytics Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

LDAP (AD) works with cn but not with sAMAccountName (OBIEE 11.1.1.6.2)

872653Aug 23 2012 — edited Aug 23 2012
Hi all,

I have configured Active Directory LDAP on OBIEE 11.1.1.6.2. With the below configuration, its works fine with NAME space SURNAME instead of NAME.SURNAME
 

Host: xxx 
Port: 389 
Principal: CN=obiee,ou=uservice, ou=Others, DC=xxxcity, DC=local 
User Base DN: DC=xxxcity, DC=local 
User From Name Filter: (&(cn=%u)(objectclass=user)) 
User Name Attribute : cn 
User Object Class: user 
group base DN: OU=Others, DC=xxxcity, DC=local 
Group From Name Filter: (&(cn=%g)(objectclass=group)) 
GUID Attribute: objectguid 

EM Identity Store Provider: 
user.login.attr= cn 
username.attr= cn 
If I chage only the below 3 parameter to sAMAccountName, I can see the users (name.surname) but could not login with these users. I am getting the error as that user does not find in identity store.
 
User From Name Filter: (&(sAMAccountName=%u)(objectclass=user)) 
User Name Attribute : sAMAccountName 
Group From Name Filter: (&(sAMAccountName=%g)(objectclass=group)) 
Do I have to change something else than these 3 parameter? Do I have to change "EM Identity Store Provider" parameters to sAMAccountName?

Any help is really appreciated.

Thanks in advance.
Comments
Locked Post
New comments cannot be posted to this locked post.