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

KB41895: When importing and synchronizing users from LDAP in MicroStrategy, the imported LDAP users are not correctly renamed when using a custom imported LDAP attribute for 'import user name as'.


Community Admin

• Strategy


When importing and synchronizing users from LDAP in MicroStrategy the imported LDAP users are not correctly renamed when using a custom imported LDAP attribute for 'import user name as'.

SYMPTOM:
When importing and synchronizing users from LDAP in Strategy 9.x, the imported LDAP users are not properly renamed when using a custom imported LDAP attribute. Instead the users are imported to Strategy using the default attribute for the LDAP server. This behavior is configured as shown below:
 

ka04W000000OeEXQA0_0EM4400000029gB.png

 
CAUSE:
There are many causes for this type of behavior but in this instance the authentication user was incorrectly specified by not using the distinguished name (DN). As a result of not using the distinguished name for the authentication user, the attributes were not able to be configured properly for usage in Strategy. If the specified attribute cannot be found on the LDAP server, the Intelligence Server automatically defaults to importing the attribute 'cn' as the user name.
ACTION:
Ensure that the authentication user is specified using the distinguished name and not any other attribute. Also, in order to utilize attributes from the LDAP server in Strategy, they must be configured under the LDAP attributes menu shown below:
 

ka04W000000OeEXQA0_0EM4400000029g4.png

 
note: If attributes do not appear in the above menu this indicates that the authentication user does not have access the attributes and/or that the distinguished name (DN) was not used.
 
 
 


Comment

0 comments

Details

Knowledge Article

Published:

June 12, 2017

Last Updated:

June 12, 2017