GitHub user sarathkouk opened a pull request:

    https://github.com/apache/cloudstack/pull/1305

        test/integration/smoke/AUTOMATIONConfigfiles/

     LDAP : Auto Import and Trust AD
    
     As of now, Cloudstack can automatically import LDAP users based on the
     configuration to a domain or an account. However, any new users in LDAP
     aren't automatically reflected. The admin has to manually import them
     again.
     This feature enables admin to map LDAP group/OU to a CloudStack domain
     and any changes are reflected in ACS as well.
    FS: 
https://cwiki.apache.org/confluence/display/CLOUDSTACK/WIP%3A+LDAP%3A+Trust+AD+and+Auto+Import
    
    
    Test Results 
    test_01_ldap (integration.component.test_ldap_autoImport.TestLdap1) ... === 
TestName: test_01_ldap | Status : SUCCESS ===
    ok
    test_02_ldap (integration.component.test_ldap_autoImport.TestLdap1) ... === 
TestName: test_02_ldap | Status : SUCCESS ===
    ok
    test_03_ldap (integration.component.test_ldap_autoImport.TestLdap1) ... === 
TestName: test_03_ldap | Status : SUCCESS ===
    ok
    test_04_ldap (integration.component.test_ldap_autoImport.TestLdap1) ... === 
TestName: test_04_ldap | Status : SUCCESS ===
    ok
    test_05_ldap (integration.component.test_ldap_autoImport.TestLdap1) ... === 
TestName: test_05_ldap | Status : SUCCESS ===
    ok
    test_06_ldap (integration.component.test_ldap_autoImport.TestLdap1) ... === 
TestName: test_06_ldap | Status : SUCCESS ===
    ok
    test_07_ldap (integration.component.test_ldap_autoImport.TestLdap1) ... === 
TestName: test_07_ldap | Status : SUCCESS ===
    ok
    test_09_ldap (integration.component.test_ldap_autoImport.TestLdap1) ... === 
TestName: test_09_ldap | Status : SUCCESS ===
    ok
    test_12_ldap (integration.component.test_ldap_autoImport.TestLdap1) ... === 
TestName: test_12_ldap | Status : SUCCESS ===
    ok
    test_13_ldap (integration.component.test_ldap_autoImport.TestLdap1) ... === 
TestName: test_13_ldap | Status : SUCCESS ===
    ok
    test_14_ldap (integration.component.test_ldap_autoImport.TestLdap1) ... === 
TestName: test_14_ldap | Status : SUCCESS ===
    ok
    test_15_ldap (integration.component.test_ldap_autoImport.TestLdap1) ... === 
TestName: test_15_ldap | Status : SUCCESS ===
    ok


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

    $ git pull https://github.com/sarathkouk/cloudstack ldap

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

    https://github.com/apache/cloudstack/pull/1305.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 #1305
    
----
commit 4d0d7b0acb45db1a5d11e373d01cd8aa75ba458d
Author: sarath <sarathk...@gmail.com>
Date:   2015-10-09T14:23:04Z

        test/integration/smoke/AUTOMATIONConfigfiles/
    'LDAP: Auto Import and Trust AD' automation
    
    'LDAP:Auto Import and Trust AD' automation 2
    
     LDAP : Auto Import and Trust AD
    
     As og now, CloudStack can automatically import LDAP users based on the
     configuration to a domain or an account. However, any new users in LDAP
     aren't automatically reflected. The admin has to manually import them
     again.
     This feature enables admin to map LDAP group/OU to a CloudStack domain
     and any changes are reflected in ACS as well.
    
    Deleting log folder that was added by mistake
    
    LDAP : Auto IMport and Trust AD
        As of now, CloudStack can automatically import LDAP users based on the
    configuration to a domain or an account. However, any new users in LDAP
    aren't automatically reflected. The admin has to manually import them
    again.
    This feature enables admin to map LDAP group/OU to a CloudStack domain and
    any changes are reflected in ACS as well.
    
    LDAP : Trust AD and Auto Import
    
    LDAP : Trust AD and Auto Import
    
    Auto pep8 corrections for test_ldap_autoImport.py

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to