[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-6634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14102130#comment-14102130
 ] 

ASF GitHub Bot commented on CLOUDSTACK-6634:
--------------------------------------------

GitHub user karuturi opened a pull request:

    https://github.com/apache/cloudstack-docs-admin/pull/15

    CLOUDSTACK-6634

    updated the ldap section in admin guide

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/karuturi/cloudstack-docs-admin 4.3-ldap-doc

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cloudstack-docs-admin/pull/15.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #15
    
----
commit 145a0bbf2a73aeac4a61012eb358c20034a9bf63
Author: Rajani Karuturi <rajanikarut...@gmail.com>
Date:   2014-08-19T10:57:43Z

    CLOUDSTACK-6634
    
    updated the ldap section in admin guide

----


> DOC: update the ldap section of the admin guide
> -----------------------------------------------
>
>                 Key: CLOUDSTACK-6634
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6634
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: Doc
>    Affects Versions: 4.3.0
>            Reporter: Rajani Karuturi
>            Assignee: Rajani Karuturi
>              Labels: ldap
>             Fix For: 4.4.0
>
>
> http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/4.3/accounts.html#using-an-ldap-server-for-user-authentication
> there are changes/enhancements in the way ldap server is configured since 4.3 
> documentation needs to be updated with the latest info.
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/LDAP+user+provisioning



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to