Return-Path: Delivered-To: apmail-jakarta-jmeter-dev-archive@www.apache.org Received: (qmail 68978 invoked from network); 2 Oct 2004 12:53:30 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 2 Oct 2004 12:53:30 -0000 Received: (qmail 76003 invoked by uid 500); 2 Oct 2004 12:53:30 -0000 Delivered-To: apmail-jakarta-jmeter-dev-archive@jakarta.apache.org Received: (qmail 75976 invoked by uid 500); 2 Oct 2004 12:53:29 -0000 Mailing-List: contact jmeter-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "JMeter Developers List" Reply-To: "JMeter Developers List" Delivered-To: mailing list jmeter-dev@jakarta.apache.org Received: (qmail 75962 invoked by uid 500); 2 Oct 2004 12:53:29 -0000 Received: (qmail 75959 invoked by uid 99); 2 Oct 2004 12:53:29 -0000 X-ASF-Spam-Status: No, hits=-10.0 required=10.0 tests=ALL_TRUSTED,NO_REAL_NAME X-Spam-Check-By: apache.org Received: from [209.237.227.194] (HELO minotaur.apache.org) (209.237.227.194) by apache.org (qpsmtpd/0.28) with SMTP; Sat, 02 Oct 2004 05:53:28 -0700 Received: (qmail 68961 invoked by uid 1721); 2 Oct 2004 12:53:27 -0000 Date: 2 Oct 2004 12:53:27 -0000 Message-ID: <20041002125327.68960.qmail@minotaur.apache.org> From: sebb@apache.org To: jakarta-jmeter-cvs@apache.org Subject: cvs commit: jakarta-jmeter/xdocs/usermanual build-ldapext-test-plan.xml component_reference.xml X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N sebb 2004/10/02 05:53:27 Modified: xdocs/usermanual build-ldapext-test-plan.xml component_reference.xml Log: See bug 30952 - applied documentation updates Revision Changes Path 1.2 +13 -4 jakarta-jmeter/xdocs/usermanual/build-ldapext-test-plan.xml Index: build-ldapext-test-plan.xml =================================================================== RCS file: /home/cvs/jakarta-jmeter/xdocs/usermanual/build-ldapext-test-plan.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- build-ldapext-test-plan.xml 17 Aug 2004 21:44:03 -0000 1.1 +++ build-ldapext-test-plan.xml 2 Oct 2004 12:53:27 -0000 1.2 @@ -51,6 +51,15 @@ LDAP tutorial which shortly explains the several LDAP operations that can be used in building a complex testplan.

+

+Take care when using LDAP special characters in the distinghuished name, in that case (eg, you want to use a + sign in a +distinghuished name) you need to escape the character by adding an "\" sign before that character. +extra exeption: if you want to add a \ character in a distinghuised name (in an add or rename operation), you need to use 4 backslashes. +examples: +cn=dolf\+smits to add/search an entry with the name like cn=dolf+smits +cn=dolf \\ smits to search an entry with the name cn=dolf \ smits +cn=c:\\\\log.txt to add an entry with a name like cn=c:\log.txt +

@@ -353,8 +362,8 @@
  • enter the name of the entry, relative to the baseDN, in the "old entry name-Field".
    -that is, if you want to remove "cn=john doe,ou=people,dc=siemens,dc=com", and you set the baseDN to "dc=siemens,dc=com", -you need to enter "cn=john doe,ou=people" in the Delete-field. +that is, if you want to rename "cn=john doe,ou=people,dc=siemens,dc=com", and you set the baseDN to "dc=siemens,dc=com", +you need to enter "cn=john doe,ou=people" in the old entry name-field.
  • enter the new name of the entry, relative to the baseDN, in the "new distinghuised name-Field".
    1.94 +136 -1 jakarta-jmeter/xdocs/usermanual/component_reference.xml Index: component_reference.xml =================================================================== RCS file: /home/cvs/jakarta-jmeter/xdocs/usermanual/component_reference.xml,v retrieving revision 1.93 retrieving revision 1.94 diff -u -r1.93 -r1.94 --- component_reference.xml 26 Jun 2004 23:25:45 -0000 1.93 +++ component_reference.xml 2 Oct 2004 12:53:27 -0000 1.94 @@ -297,6 +297,134 @@ + + This Sampler can send all 8 different LDAP request to a LDAP server. It is an extended version of the LDAP sampler, + therefore it is harder to configure, but can be made much closer resembling a real LDAP session. +

    If you are going to send multiple requests to the same LDAP server, consider + using an + Configuration Element so you do not have to enter the same information for each + LDAP Request.

     + +

    There are nine test operations defined. These operations are given below:

    +
      +
    1. Thread bind
      2. +

      Any LDAP request is part of a LDAP session, so the first thing that should be done is starting a session to the LDAP server. + For starting this session a thread bind is used, which is equal to the LDAP "bind" operation. + The user is requested to give a username (Distinghuised name) and password, + which will be used to initiate a session. + When no password, or the wrong password is specified, an anonymous session is started. Take care, + omitting the password will not fail this test, a wrong password will.

      + + Descriptive name for this sampler that is shown in the tree. + The name (or IP-address) of the LDAP server. + The port number that the LDAP server is listening to. If this is omitted + JMeter assumes the LDAP server is listening on the default port(389). + The distinghuished name of the base object that will be used for any subsequent operation. + It can be used as a starting point for all operations. You cannot start any operation on a higher level than this DN! + Full distinghuished name of the user as which you want to bind. + Password for the above user. If omitted it will result in an anonymous bind. + If is is incorrect, the sampler will return an error and revert to an anonymous bind. + + +
    2. Thread unbind
      3. +

      This is simply the operation to end a session. + It is equal to the LDAP "unbind" operation.

      + + Descriptive name for this sampler that is shown in the tree. + + +
    3. Single bind/unbind
      4. +

      This is a combination of the LDAP "bind" and "unbind" operations. + It can be used for an authentication request/password check for any user. It will open an new session, just to + check the validity of the user/password combination, and end the session again.

      + + Descriptive name for this sampler that is shown in the tree. + Full distinghuished name of the user as which you want to bind. + Password for the above user. If omitted it will result in an anonymous bind. + If is is incorrect, the sampler will return an error. + + +
    4. Rename entry
      5. +

      This is the LDAP "moddn" operation. It can be used to rename an entry, but + also for moving an entry or a complete subtree to a different place in + the LDAP tree.

      + + Descriptive name for this sampler that is shown in the tree. + The current distinghuished name of the object you want to rename or move, + relative to the given DN in the thread bind operation. + The new distinghuished name of the object you want to rename or move, + relative to the given DN in the thread bind operation. + + +
    5. Add test
      6. +

      This is the ldap "add" operation. It can be used to add any kind of + object to the LDAP server.

      + + Descriptive name for this sampler that is shown in the tree. + Distinghuised name of the object you want to add, relative to the given DN in the thread bind operation. + A list of attributes and their values you want to use for the object. + If you need to add a multiple value attribute, you need to add the same attribute with their respective + values several times to the list. + + +
    6. Delete test
      7. +

      This is the LDAP "delete" operation, it can be used to delete an + object from the LDAP tree

      + + Descriptive name for this sampler that is shown in the tree. + Distinghuished name of the object you want to delete, relative to the given DN in the thread bind operation. + + +
    7. Search test
      8. +

      This is the LDAP "search" operation, and will be used for defining searches.

      + + Descriptive name for this sampler that is shown in the tree. + Distinghuished name of the subtree you want your + search to look in, relative to the given DN in the thread bind operation. + searchfilter, must be specified in LDAP syntax. + Use 0 for baseobject-, 1 for onelevel- and 2 for a subtree search. (Default=0) + Specify the maximum number of results you want back from the server. (default=0, which means no limit.) When the sampler hits the maximum number of results, it will fail with errorcode 4 + Specify the maximum amount of (cpu)time (in miliseconds) that the server can spend on your search. Take care, this does not say anything about the responsetime. (default is 0, which means no limit) + Specify the attributes you want to have returned, seperated by a semicolon. An empty field will return all attributes + Whether the object will be returned (true) or not (false). Default=false + If true, it will dereference aliases, if false, it will not follow them (default=false) + + . +
    8. Modification test
      9. +

      This is the LDAP "modify" operation. It can be used to modify an object. It + can be used to add, delete or replace values of an attribute.

      + + Descriptive name for this sampler that is shown in the tree. + Distinghuished name of the object you want to modify, relative + to the given DN in the thread bind operation + The attribute-value-opCode triples. The opCode can be any + valid LDAP operationCode (add, delete or replace). If you don't specify a value with a delete operation, + all values of the given attribute will be deleted. If you do specify a value in a delete operation, only + the given value will be deleted. If this value is non-existent, the sampler will fail the test. + + +
    9. compare
      10. +

      This is the LDAP "compare" operation. It can be used to compare the value + of a given attribute with some already known value. In reality this is mostly + used to check whether a given person is a member of some group. In such a case + you can compare the DN of the user as a given value, with the values in the + attribute "member" of an object of the type groupOfNames. + If the compare operation fails, this test fails with errorcode 49.

      + + Descriptive name for this sampler that is shown in the tree. + The current distinghuished name of the object of + which you want to compare an attribute, relative to the given DN in the thread bind operation. + In the form "attribute=value" + +
    + + + Building a Ldap Test Plan + + + +     + @@ -1347,6 +1475,13 @@ + + +

    The LDAP Extended Request Defaults component lets you set default values for extended LDAP testing. See the .

    +     + +     +

    The Java Request Defaults component lets you set default values for Java testing. See the .

    --------------------------------------------------------------------- To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org