You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Ian Duffy (JIRA)" <ji...@apache.org> on 2013/07/23 17:40:50 UTC
[jira] [Closed] (CLOUDSTACK-1930) LDAP docs are missing some steps
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ian Duffy closed CLOUDSTACK-1930.
---------------------------------
Resolution: Not A Problem
Fix was only for 3.x and 4.0 as stated by the commenter.
Closing as its not required in 4.1 and 4.2
> LDAP docs are missing some steps
> --------------------------------
>
> Key: CLOUDSTACK-1930
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1930
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Doc
> Reporter: Jessica Tomechak
> Assignee: Ian Duffy
>
> 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="3.0.5.20120904142539">
> - <ldapconfig>
> <hostname>192.168.21.72</hostname>
> <port>389</port>
> <port>false</port>
> <searchbase>OU=Testing,DC=xendesktop,DC=internal</searchbase>
> <queryfilter>(&(mail=%e))</queryfilter>
> <binddn>CN=Administrator,CN=users,DC=xendesktop,DC=internal</binddn>
> </ldapconfig>
> </ldapconfigresponse>
> 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="com.cloud.server.auth.MD5UserAuthenticator"/>
> To
> <adapter name="MD5" class="com.cloud.server.auth.PlainTextUserAuthenticator"/>
> 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: http://www.atlassian.com/software/jira