Problem using a group which has a space in it's DN when using LDAP Group mappings in UCS 1.4

[dors]

Hey,

We've been implementing LDAP authentication (Active Directory) using LDAP group mapping in UCS 1.4, and we've noticed that when using a group which has a DN with a space in it (such as "UCS Admins") it wouldn't authenticate the user with the appropriate role.

Using a DN without spaces (such as "UCSAdmins"), works just fine.

I should mention that having a base DN with spaces works just fine as well, it's just the group mappings that doesn't work.

I should also mention that Cisco's "Quick guide to configuring ldap for ucs 1.4" shows an example in which the group's DN doesn't include a space.

Is there a workaround available which can make it possible using a group which has a space in it's name?

Thanks,

Dor

[Roman Rodichev]

Have you tried putting quotation marks around it? This usually fixes this issue in Cisco's CLIs

[dors]

Hey Roman,

Thanks for your prompt reply.

We've tried putting quotes using UCSM which is not possible at all - not for the entire entry nor for the part with spaces.

We've also tried using CLI ("scope security/ldap/ldap-group") where you have to put quotes if you use a DN with spaces, and it still doesn't work. Furthermore, we tried adding quotes only to the part with the spaces, i.e. - CN="UCS Admins",OU=TEST,DC=TEST. It adds the entry without an error, but shows like we would use "CN=UCS Admins,OU=TEST,DC=TEST". Anyway, it doesn't work either.

Thanks again,

Dor

[dors]

Problem solved - the user which we used to authenticate had the specific group which we used for the ldap group mapping as his primary group in Active Directory.

Once we have changed the users' primary group to another group, he was able to login and gain priveligies.

I think it should be noted that when using LDAP group mapping, the group used shouldn't be the users' primary group.

Dor