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

KB44687: When using internationalization, user name is not updated using ’Synchronize MicroStrategy User Login/User Name with LDAP’ option in LDAP authentication in MicroStrategy 9.4.1


Community Admin

• Strategy


In MicroStrategy 9.4.1, the user name is not updated when using the 'Synchronize MicroStrategy User Login/User Name with LDAP' option with internationalization.

SYMPTOM:
In Strategy 9.4.1, the user name is not updated when using the 'Synchronize Strategy User Login/User Name with LDAP' option with internationalization.
STEPS TO REPRODUCE:

  • Enable the 'Synchronize Strategy User Login/User Name with LDAP' option in LDAP – Import – Import/Synchronize category in Intelligence Server Configuration, as shown in the image below:
     
ka04W000000ObcGQAS_0EM440000002Cfk.png
  • Select ‘Use LDAP Authentication’ in Strategy Desktop, as shown in the image below:
ka04W000000ObcGQAS_0EM440000002CfX.png
  • In Active Directory, set the display name of ‘abcUser1’ to ‘AAA’.
     
  • Login as ‘abcUser1’ in Japanese interface.
ka04W000000ObcGQAS_0EM440000002Cfq.png
  • Full name is displayed as ‘AAA’ as specified.
ka04W000000ObcGQAS_0EM440000002Cfa.png
  • Update the display name of ‘abcUser1’ user to ‘BBB’.
     
  • Re-login to Strategy Desktop in Japanese interface. Note that full name is not updated to ‘BBB’ while the modification time is updated.
ka04W000000ObcGQAS_0EM440000002Cfh.png
  • Switch to English interface and find that the English full name is updated to ‘BBB’, as shown in the image below:
ka04W000000ObcGQAS_0EM440000002Cfj.png

 
CAUSE:
This is a known issue with Strategy 9.4.1
ACTION:
This issue has been fixed in Strategy version 10.x
Please consider upgrading to Strategy 10.x to benefit from the fix
 


Comment

0 comments

Details

Knowledge Article

Published:

May 28, 2017

Last Updated:

May 28, 2017