08 Dec, 2006

1 commit


07 Dec, 2006

1 commit


05 Dec, 2006

3 commits

  • - It fixes problems with base DN registration when attempting to use nested
      backends.
    
    - It changes the terminology that is in use.  Previously, the term "suffix" was
      used everywhere, even when it wasn't really correct.  Now "naming context" is
      used when it's talking about a top-level base DN, and "base DN" is used for
      any base DN regardless of whether it's a naming context.
    
    - It adds a new ds-private-naming-contexts operational attribute to the root
      DSE to list the private naming contexts defined in the server.
    
    - It updates the backend API to get rid of the abstract supportsControl and
      supportsFeature methods and replace them with a default concrete
      implementation.
    
    
    OpenDS Issue Numbers:  546, 750
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@844 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • as specified by RFC4512 :
    
     SyntaxDescription = LPAREN WSP
             numericoid                 ; object identifier
             [ SP "DESC" SP qdstring ]  ; description
             extensions WSP RPAREN      ; extensions
    
    see SYNTAX_LDAP_SYNTAX_OID from org.opends.server.schema.LDAPSyntaxTest.java
    
    Issue 640.
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@840 41b1ffd8-f28e-4786-ab96-9950f0a78031
    dugan
     
  • -1 when attempting to get the last login time for a user when it isn't possible
    to do so for some reason.  Even though the documentation said it would return
    -1 in this case, it was actually returning the creation timestamp for the
    entry.
    
    OpenDS Issue Number:  1055
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@839 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     

30 Nov, 2006

9 commits


29 Nov, 2006

1 commit


22 Nov, 2006

1 commit

  • …formatting of the messages that appear in the progress panel.
    
    This is done mainly for two reasons:
    
    1. The code in the Installer class should not control the format used (HTML, plain text, etc.) which is more related to the pure UI.
    2. Be able to share this formatting code for the graphical installation and also the uninstallation so that we have the same look and feel in both without code duplication." /usr/project/iplanet/ws/jvl/EclipseWorkspace/OpenDS/src/quicksetup/org/opends/quicksetup/installer/Installer.java /usr/project/iplanet/ws/jvl/EclipseWorkspace/OpenDS/src/quicksetup/org/opends/quicksetup/installer/offline/OfflineInstaller.java /usr/project/iplanet/ws/jvl/EclipseWorkspace/OpenDS/src/quicksetup/org/opends/quicksetup/installer/webstart/WebStartInstaller.java /usr/project/iplanet/ws/jvl/EclipseWorkspace/OpenDS/src/quicksetup/org/opends/quicksetup/QuickSetup.java /usr/project/iplanet/ws/jvl/EclipseWorkspace/OpenDS/src/quicksetup/org/opends/quicksetup/ui/CurrentStepPanel.java /usr/project/iplanet/ws/jvl/EclipseWorkspace/OpenDS/src/quicksetup/org/opends/quicksetup/ui/ProgressPanel.java /usr/project/iplanet/ws/jvl/EclipseWorkspace/OpenDS/src/quicksetup/org/opends/quicksetup/ui/QuickSetupDialog.java
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@771 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     

21 Nov, 2006

2 commits

  • …formatting of the messages that appear in the progress panel.
    
    This is done mainly for two reasons:
    
    1. The code in the Installer class should not control the format used (HTML, plain text, etc.) which is more related to the pure UI.
    2. Be able to share this formatting code for the graphical installation and also the uninstallation so that we have the same look and feel in both without code duplication.
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@769 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • Add some code to improve the displayed download progress bar.  Know the code takes into consideration the actual size of the jar files instead of considering that all have the same size.
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@765 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     

20 Nov, 2006

6 commits

  • …ything should work fine from the first time. 
    
    If it does not work, just throw an exception 
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@756 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • bug in which "TH" was incorrectly mapped to a capital letter "O" (oh) instead
    of the number "0" (zero).
    
    This fix was provided by Terry Sigle (username tsigle).
    
    OpenDS Issue Number:  690
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@754 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • …Java WebStart Setup.  There were two issues with the existing code:
    
    1. We used to pass the parameter 'overallPercent' of the validating method of WebStartDownloader to calculate the downloaded percentage.  This is wrong as this value corresponds to the validation percentage.  This produced to sometimes display a downloaded 0 % while we were validating the files.
    
    2. We did not provide any additional feedback while we were validating a jar file.  This produced the displayed message to be stuck at 'Downloading: 33 % Completed' or 'Downloading: 66 % Completed'.
    
    
    The fix for the first issue is trivial: the value indicating the percentage of downloaded files is not modified in the validating method nor in the upgradingArchive method of the WebStartDownloader class.
    
    The fix for the second issue consists of adding some interfaces to WebStartDownloader to know whether we are downloading a jar file, validating a jar file or upgrading a jar file.  In addition to that two methods have been added to know how much of the current jar file has been validated or upgraded.  This way we can have know a more complete (and lively) message during download.  When we are just downloading a jar file the message will stay the same.  For example:
    
    
    'Downloading: 23 % Completed'
    
    But when we are validating a jar file the message will be:
    
    'Downloading: 33% Completed - Validating file: 89 % Completed.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@753 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • other LDAP client tools.
    
    OpenDS Issue Number:  1023
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@750 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • --bindPasswordFile argument from -W to -j in order to be consistent with the
    usage for all of the other command-line tools.
    
    OpenDS Issue Number:  1022
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@749 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • database with sample data, like the GUI version.
    
    OpenDS Issue Number:  1021
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@748 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     

17 Nov, 2006

3 commits

  • the correct name.
    
    OpenDS Issue Number:  993
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@746 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • * Add a new quicksetup.jar file that can be used for both Web Start and local installations of Open DS.
    
    * Modify the setup script so that now they will launch by default the graphical setup.  If an error occurs (because for instance we do not have access to the display) or if the user specifies the --cli option then we will use the cli based setup (the one we had until today).
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@744 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • waiting-changes that publish the number of updates known by the changelog
    server that have not yest been sent to each ldap server because they are too slow to replay them.
    
    This is calculated from the list of changes in memory when this list is small
    enough. However when this list becomes too large it is not possible to keep
    all the changes in memory and the changes therefore goes to disk.
    This monitoring information therefore becomes unavailable and currently returns MAXINT.
    
    This is unfortunate because this is the time when it is the most important.
    
    Unfortunately the Java edition of the berkeley DB does not provide a way to
    know the record number of a given db entry and therefore we can't rely on the DB
    to tell us how many changes stay in the db after the current change.
    
    This fix therefore change the format of the ChangeNumber so that the ChangeNumber
    now uses consecutive numbers for its seqnum part.
    
    The number of missing changes can therefore be calculated by a simple substraction
    of the current seqnum and the largest seqnum.
    the drawback of this method is that it is only accurate if the majority of update
    operations done on the masters are successfull because this method also count the failed
    operations.
    
    This fix also modify the ProtocolWindowTest in order to add  tests of this waiting-changes
    monitoring information.
    
    This fix also makes the size of the memory queue of messages configurable.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@741 41b1ffd8-f28e-4786-ab96-9950f0a78031
    gbellato
     

16 Nov, 2006

3 commits

  • displaying usage information in the new installer.
    
    OpenDS Issue Number: 1017
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@740 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • to count the number of matching entries.  The count will be displayed as a
    comment at the end of the results, and will also be used as the exit code for
    the tool.  This addresses issue #1013.
    
    This commit also includes test cases for this issue as well as the use of
    alternate human-readable names for certain types of controls.  These test cases
    are more applicable to issue #989, but need the --countEntries option for
    verifying that the LDAP subentries control is working as expected.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@731 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • a more user-friendly name instead of the numeric OID when using the "-J" or
    "--control" option.  These changes include:
    
    - "accountusable" or "accountusability" may be used to specify the account
      usable request control
    - "authzid" or "authorizationidentity" may be used to specify the authorization
      identity request control
    - "noop" or "no-op" may be used to specify the LDAP no-op control
    - "subentries" may be used to specify the LDAP subentries request control
    - "managedsait" may be used to specify the manage DSA IT control
    - "pwpolicy" or "password policy" may be used to specify the password policy
      request control
    - "subtreedelete" or "treedelete" may be used to specify the subtree delete
      control
    
    OpenDS Issue Number:  989
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@730 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     

15 Nov, 2006

5 commits

  • the "--controls" argument to "--control", since each instance only allows the
    user to specify information about a single control.  Issue #1009.
    
    Update the LDAPSearch, LDAPModify, LDAPCompare, and LDAPDelete tools to allow
    multiple instances of the "-J"/"--control" argument to specify multiple
    arbitrary controls.  Issue #1010.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@727 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • returns true whenever it is queried for a control that it actually supports
    instead of always blindly returning false.
    
    OpenDS Issue Number:  1011
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@726 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • "--saslOption", since each occurrence only specifies a single option.
    
    OpenDS Issue Number:  1008
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@725 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • so it is not displayed in the usage information (it is automatically provided
    by the shell script/batch file used to launch the tool, so the user doesn't
    need to provide it or be aware of it).
    
    OpenDS Issue Number:  1007
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@724 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • instead of pwdPolicySubentry for indicating which password policy should be
    applied for a given user.  The new attribute is not marked NO-USER-MODIFICATION
    so that it can be directly altered by administrators in addition to having a
    value populated by a virtual attribute.  The pwdPolicySubentry attribute is
    defined in the IETF draft as NO-USER-MODIFICATION and is only intended to be
    virtually defined, making it more difficult to configure a special policy for
    an individual user.
    
    This also eliminates the possibility that clients will see this attribute and
    will expect the corresponding password policy configuration to be based on the
    specification in the IETF draft, which is not the case for OpenDS.
    
    OpenDS Issue Number:  1003
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@723 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     

14 Nov, 2006

1 commit

  • - 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
     

13 Nov, 2006

2 commits

  • server along with their base DNs, as well as list all base DNs for a given
    backend ID or list the backend ID for a given base DN.
    
    Reviewed By:  David Ely
    OpenDS Issue Number:  44
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@706 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • before synchronization code was in 2 packages :
    org.opends.server.synchronization and org.opends.server.changelog
    
    It was not clear that the code in the changelog package is part of the synchronization
    also some code in both of these packages are actually used by both sides of the synchronization.
    
    To make this better (and as said in the synchronization meeting) the code is now split in 4
    packages that are all below : org.opends.server.synchronization
    - synchronization.changelog contain the code running on the changelog side
    - synchronization.plugin contain the code running on the DS side.
    - synchronization.protocol contain the code used by both side to exchange information.
    - synchronization.common contain utilities that can be used by any of the first 3 packages.
    
    Hopefully this should make the synchronization code more easy to understand.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@704 41b1ffd8-f28e-4786-ab96-9950f0a78031
    gbellato
     

11 Nov, 2006

1 commit


10 Nov, 2006

1 commit

  • 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