Change By: Marco Miller (27/May/14 7:25 PM)
Description: Scenario  1 : user can log-in to Jenkins as admin after AD security configured- <br>
     * Given a Jenkins instance that is of type=existing<br>
     *  And a pre-installed active-directory plugin version 1.34 (1.37 failed)<br>
     *  And an AD security configuration that is matrix-based (project)<br>
     *  And a user added to that matrix so she can Administer<br>
     * When I save such an AD security configuration<br>
     * Then that user can log-in to that Jenkins as admin.

Scenario  2 : user can log-in to Jenkins as admin group member after AD security configured- <br>
     * Given a Jenkins instance that is of type=existing<br>
     *  And a pre-installed active-directory plugin version 1.34 (1.37 failed)<br>
     *  And an AD security configuration that is matrix-based (project)<br>
     *  And a group added to that matrix so its members can Administer<br>
     *  And a
Scenario 3:  user  being a member of that group<br>
     * When I save such an AD security configuration<br>
     * Then that user can
 wannabe cannot  log-in to  that  Jenkins  as admin.  after AD security configured-
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

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to