EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB44218: When defining an LDAP filter using a group name with special characters, the group name is not correctly read and it returns an "Incorrect login/password" error message in the DSSErrors.log in MicroStrategy 9.x


Community Admin

• Strategy


When defining an LDAP filter using a group name with special characters like parenthesis (for example "GroupName(MicroStrategy)"), the group name is not correctly read and it returns an "Incorrect login/password" error message in the DSSErrors.log. 

SYMPTOM:
 
When defining an LDAP filter using a group name with special characters like parenthesis (for example "GroupName(Strategy)"), the group name is not correctly read and it returns an "Incorrect login/password" error message in the DSSErrors.log. 
 
CAUSE: 
 
This is caused by the way the LDAP queries are built. By default parenthesis are used as part of the "AND" clause. Special characters can be used as different wildcard types. For example:
 


(&(objectCategory=person)(objectClass=user))   ,     (telephoneNumber=(*)*-*)

 
ACTION:
 
An enhancement request has been logged to provide the ability to use special characters in the LDAP filter. Contact Strategy Technical Support for an update on this request.
 
WORKAROUND: 
 
In order to use special characters in the group names, they must be escaped by the use of a "/". For example:
 

memberOf=CN=GroupName \(Strategy\)

  
 
This issue is being tracked by internal reference number 767978.


Comment

0 comments

Details

Knowledge Article

Published:

May 5, 2017

Last Updated:

May 5, 2017