cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Musayev, Ilya" <>
Subject RE: [jira] [Created] (CLOUDSTACK-1930) LDAP docs are missing some steps
Date Thu, 04 Apr 2013 04:46:43 GMT

The hack/fix below applies only to  3.x and 4.0.

4.1 and 4.2 - no longer require this specific change


-----Original Message-----
From: Jessica Tomechak (JIRA) [] 
Sent: Wednesday, April 03, 2013 9:44 PM
Subject: [jira] [Created] (CLOUDSTACK-1930) LDAP docs are missing some steps

Jessica Tomechak created CLOUDSTACK-1930:

             Summary: LDAP docs are missing some steps
                 Key: CLOUDSTACK-1930
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: Doc
            Reporter: Jessica Tomechak

In the Admin Guide is a section "Using an LDAP Server for User Authentication". It tells how
to set up the API call and covers LDAP query concepts. However, it skips a couple of configuration
steps which are required to enable LDAP. The below were provided by Stuart Jennings. 

**These steps should be tested and checked to be sure they are still up to date**

(Set up and call ldapConfig ... already covered in the Admin Guide)

Wait for a successful response and then restart cloud-management service – below is an example
of the response you will receive if the API command was a success. 

  <?xml version="1.0" encoding="ISO-8859-1" ?>
- <ldapconfigresponse cloud-stack-version="">
- <ldapconfig>

Amend SharedFunctions and Components.xml Config

Next edit the sharedFunctions.js file – found in /usr/share/cloud/management/webapps/client/scripts
so the md5HashedLogin = false

Example -
// Default password is MD5 hashed.  Set the following variable to false to disable this.
var md5Hashed = true;
var md5HashedLogin = false;

Next edit the /etc/cloud/management/components.xml and change <adapter name="MD5" class=""/>
<adapter name="MD5" class=""/>

Restart cloud-management 

Finally make sure that the user accounts within CloudPlatform have email addresses which match
the mail attributes in active directory.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators For more information
on JIRA, see:

View raw message