onitake commented on a change in pull request #67: short description of the evolution of LDAP bindings URL: https://github.com/apache/cloudstack-documentation/pull/67#discussion_r313433008
########## File path: source/adminguide/accounts.rst ########## @@ -279,17 +279,99 @@ or ApacheDS to authenticate CloudStack end-users. CloudStack will search the external LDAP directory tree starting at a specified base directory and gets user info such as first name, last name, email and username. -Starting with CloudStack 4.11, an ldap connection per domain can be -defined. +Starting with CloudStack 4.11, an LDAP connection per domain can be +defined. In this domain autosync per account can be configured, +keeping the users in the domain up to date with their group membership +in LDAP. +.. Note:: A caveat with this is that ApacheDS does not yet support the +virtual 'memberOf' attribute needed to check if a user moved to +another account. Microsoft AD and OpenLDAP as well as OpenDJ do support +this. It is a planned feature for ApacheDS that can be tracked in +https://issues.apache.org/jira/browse/DIRSERVER-1844. + +There are now three ways to link LDAP users to CloudStack users. These +three ways where developed as extensions on top of each other. + +To authenticate, in all three cases username and password entered by +the user are used. + +#. manual import. A user is explicitely mapped to a domain/account + and created as a user in that account + + #. CloudStack does a search for a user with the given username. + + #. If it exists, it checks if the user is enabled Review comment: I think there should be a full stop here. Same thing for all other bullet points. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
