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

KB36568: "An error occurred during authentication. Please contact your administrator: LDAP Component not found or is not V3 compliant" error occurs when logging in to MicroStrategy Developer or Web 9.x/10.x


Stefan Zepeda

Salesforce Solutions Architect • Strategy


KB describing what o do when experiencing "LDAP Component not found or is not V3 compliant." error message when logging into MicroStrategy Developer or Web.

SYMPTOM:
When logging in to Strategy Developer or Web 9.x/10.x using LDAP authentication the following error occurs:
 
 


An error occurred during authentication.  Please contact your administrator: LDAP Component not found or is not V3 compliant.

 
CAUSE:
This issue may be caused by using an LDAP connectivity driver and Strategy Intelligence Server 9.x operating system configuration which is unsupported. Even if an unsupported configuration successfully connects for a user in one version of Strategy, there is no guarantee it will connect in another version of Strategy.  When using an unsupported configuration the end-user assumes all risk associated with such a configuration.
 
ACTION:
Use a supported LDAP connectivity driver and operating system configuration for the Strategy Intelligence Server 9.x.  The general supported configurations are listed in the table below (consult the Strategy version specific README for the exact driver and OS versions supported):
 
 
Once a supported configuration is in place, change update the LDAP connectivity driver used by the Strategy Intelligence Server 9.x by going to: Strategy Intelligence Server Configuration > LDAP > Platform:
 


Comment

0 comments

Details

Knowledge Article

Published:

June 2, 2017

Last Updated:

June 2, 2017