15 Nov, 2006

7 commits


14 Nov, 2006

4 commits

  • - It is no longer necessary to specify the password storage scheme separately
      from the encoded value when comparing an encoded password. This makes this
      feature easier to use because it takes the data in the same format as is
      created by when encoding a clear-text password and as is stored in the
      directory.  Issue #971.
    
    - When comparing a clear-text password against an encoded version, you can now
      use the --useCompareResultCode option to cause the tool to exit with a return
      code of COMPARE_TRUE or COMPARE_FALSE, which is more useful when calling the
      utility in a script.  Previously, it would always return zero to indicate
      that the script completed successfully, regardless of whether the provided
      password matched or not.  Issue #988.
    
    - I've made the tool easier to call programmatically by adding additional
      methods that can be used to invoke it, by making it possible to avoid
      reinitializing the server, to provide alternate output and error streams (or
      eliminate the output entirely), and to return an integer value rather than
      using System.exit.  This all kind of falls under the umbrella of issue #987.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@714 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@713 41b1ffd8-f28e-4786-ab96-9950f0a78031
    gary_williams
     
  • unit tests.
    This should help making the tests more reliable without increasing their duration.
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@711 41b1ffd8-f28e-4786-ab96-9950f0a78031
    gbellato
     
  • 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@710 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     

13 Nov, 2006

6 commits


11 Nov, 2006

1 commit


10 Nov, 2006

3 commits

  • are all made under the umbrella of issue #994, but there are individual issues
    for each change.
    
    - Issue #979 -- Re-order LDAP tool arguments
      When displaying usage information for many of the LDAP tools (e.g.,
      ldapsearch, ldapmodify, etc.), the arguments were not provided in any kind of
      logical grouping.  This has been corrected so that the arguments are listed
      in a more logical ordering.
    
    - Issue #983 -- Add tool description to argument parser
      When displaying usage information for administrative tools, it now includes a
      small summary of what the tool does at the top of the argument list.
    
    - Issue #984 -- Make tool usage more compact
      Previously, the tool usage included a blank line between each argument, which
      made the usage information seem too verbose, especially for tools like
      ldapsearch with a lot of arguments.  This extra space has been removed.
      Also, many of the argument descriptions have been rewritten in an attempt to
      avoid requiring multiple lines.
    
    - Issue #985 -- Wrap long output in administrative tools when appropriate
      Update most of the output for the administrative tools so that it is easier
      to read on 80-column displays.  This primarily impacts error message, and
      cases in which the format of the output is important (e.g., LDIF output from
      ldapsearch) no changes were made.
    
    - Issue #986 -- Eliminate hard-coded strings in tools
      Some of the tools had hard-coded strings used for error and warning messages.
      They have been replaced with localizeable output from the messages files.
    
    - Issue #990 -- LDAP tools don't use trust store password
      The LDAP tools didn't provide any mechanism for specifying the PIN needed to
      access the contents of an SSL trust store.  Some types of trust stores may
      require a PIN to access them, so it is now possible to either directly
      specify the PIN or to provide the path to a PIN file.
    
    - Issue #991 -- Disconnect when running stop-ds shouldn't be an error
      When using the stop-ds script, if the server began shutting down before it
      returned a response to the client, the client would provide an error message
      making it sound like something went wrong.  The output has now been updated
      to indicate that the server is likely in the course of shutting down.
    
    - Issue #992 -- Tool usage should include the tool name rather than the class
      When displaying usage information for the administrative tools, the
      fully-qualified class name for the Java class was displayed, where the name
      of the shell script or batch file would have been more useful.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@702 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • These changes implement a window mechanism in the sycnhronization protocol.
    
    Up to now the flow control mechanism used by the synchronization
    was  the TCP flow control mechanism. However, since TCP is not aware about
    the type of the synchronization mechanism this was not allowing sending
    of ACK messages when the TCP connection was saturated.
    This was also preventing the implementation of the prioritized synchronization.
    
    With these changes the TCP windows are set to a very large value and the
    flow control is based on a configurable window size on the changelog servers
    and on the LDAP servers.
    
    These changes also add monitoring informations for the current and max window sizes.
    
    I also took the opportunity to remove most the static variables and methods that were
    preventing multi instantiation of the Changelog class.
    
    I have also added tests for the incoding/decoding of ServerStartMessage and
    ChangelogStartMessage, WindowMessage and for testing the window mechanism.
    
    Also add the possibility to choose the port number used by the LDAP server when running
    the unit test using property : org.opends.server.LdapPort
    This can be usefull for debugging purpose.
    
    reviewed by Daniel
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@700 41b1ffd8-f28e-4786-ab96-9950f0a78031
    gbellato
     
  • --configFile arguments are marked hidden since those options will be provided
    by the shell script or batch file used to launch the tool.
    
    Also, unhide the "--nodetach" option in the start-ds script and make sure that
    it will appear in all lowercase characters.
    
    OpenDS Issue Numbers:  978, 980
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@699 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     

09 Nov, 2006

11 commits


08 Nov, 2006

7 commits

  • 
    - All administrative shell scripts and batch files now have the svn:eol-style
      property set to "native".  This property was not set for some of these files.
    
    - All administrative shell scripts now have the svn:executable property set.
      Some of them did not have this property set and therefore did not have the
      executable file permission bit set.
    
    - All administrative batch files now have the svn:executable property removed.
      Some batch files inadvertently had this property set.
    
    
    OpenDS Issue Number:  970
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@686 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • administrative shell scripts were renamed to drop the ".sh" extension.
    
    OpenDS Issue Number:  967
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@685 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • CATEGORY_MASK_JEB in order to ensure they are all unique and don't conflict
    with messages in any other message file.
    
    OpenDS Issue Number:  968
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@684 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@683 41b1ffd8-f28e-4786-ab96-9950f0a78031
    boli
     
  • …or it out of the EntryID class. The nextId property is now a non static property in the RootContainer class. Each RootContainer is responsible for keeping track of the next ID and assigning new entry IDs to all entries in its EntryContainers. 
    
    The constructor for IndexIteratorAllIds now requires a RootContainer parameter.
    
    The getIterator method in EntryIDSet class is also modified so it will no longer return a IndexIteratorAllIds object if no values are added to the set.
    
    This fix also fixes the issue where performing a replaceEntryTransaction or renameEntryTransaction throws a NPE if a ModifyOperation is not specified. The backends API states that backend implementation should allow nulls for internal operations.
    
    Thanks Neil for the code review.
    
    Fix for issue 802 and issue 803
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@682 41b1ffd8-f28e-4786-ab96-9950f0a78031
    boli
     
  • 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@681 41b1ffd8-f28e-4786-ab96-9950f0a78031
    el_kaboing
     
  • Security: Min Pwd Age: Pre-test Check
    Security: Min Pwd Age: Test
    Security: Min Pwd Age: Post-test Reset
    
    The number of operations are the same as before. Previously, each of the operations was a separate test
     case. Now the operations are clustered under one of these three tests.
    
    The test names are now short, meaningful, and easily read.
    
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@680 41b1ffd8-f28e-4786-ab96-9950f0a78031
    el_kaboing
     

07 Nov, 2006

1 commit