org.forgerock / org.forgerock.opendj

13 Dec, 2006

1 commit

12 Dec, 2006

1 commit

  • 215cfb24   Publish a separate monitor entry for each connection handler, which includes ... Browse Dir » 
    the protocol, listen address/port, number of established connections, and
information about each connection.

Also, update the monitor API to make it possible to include a custom
objectclass in each monitor entry.  Connection handler monitor entries now
include the ds-connectionhandler-monitor-entry objectclass.  Backend monitor
entries now include the ds-backend-monitor-entry objectclass.

OpenDS Issue Numbers:  1066 and 1091


git-svn-id: https://svn.forgerock.org/opendj/trunk@866 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     

11 Dec, 2006

2 commits

  • e5ae1e01   The following modifications include the comments from Neil and Brian (thanks to both for your help): ... Browse Dir » 
    1. Fix a bug with the setup script.  Know this script is executable after the Web Start based installation.

2. Provide a different welcome message in the setup depending on whether we are launching the setup from the command line or Web Start.  If we are launching the command line setup we make reference in the message to the Web Start installation and provide a link to the downloads page.

3. When the setup is successful, include in the message the path of the installation as was requested by William Hathaway.

4. Try to find a valid default port  (of type []389) and not limit the search to 389.  This implies not having any explanatory message to be displayed if we cannot connect to 389.

5. Update the code to better handle bug scenarii.  Previously the code assumed that only RuntimeException could occur in case of a bug.  This is not true in the general case, so know the code handles Throwable objects to detect bugs.

6. Provide the first implementation for the Uninstaller.  Some code has been rearranged to maximize code re-use.  The first implementation of the uninstaller basically does the following:

- Display a confirmation message informing of what will happen with the installation files and the consequences of uninstalling the server.

Ask the user which parts of the server must be uninstalled.

Check if we have configuration references outside the installation path (for the moment this check is limited to database files and log files). If these references exist show them to the user and ask the user whether these 'external' files must be deteled or not.

If the server is running we ask for confirmation to stop the server and if we are in windows we ask the user to provide a DN and a password to authenticate.

If the user continues and the server is running the code calls stop-ds script, if the script succeeds the code tries to delete the files in the installation that the user wanted to uninstall and  in the case there are external files to the installation path and the user wants to delete them delete also these external files.

If everything works properly the uninstaller will delete all the files except the <install-root>/lib/quicksetup.jar and <install-root>/lib/OpenDS.jar file.

OpenDS.jar file is required by the command line uninstaller to share some code.

I preferred not to try to delete these files from the scripts as we cannot provide proper feedback (for instance localization) if we encounter a problem deleting these files.

In both cases we inform the user that there are some files that must be deleted manually.

7. Provide the code to launch uninstall through command line that is analogous in terms of interaction to the graphical one.

I have included two scripts to launch the uninstallation.  The uninstall script for Unix is very similar to the setup script.  However the uninstall.bat script has a difference with setup.bat.

The difference is that I limit the class path to include only quicksetup.jar.  This is done because I have not found a way to delete the jar files that are in the class path of the java application using pure java code, so as the uninstaller does only require OpenDS.jar and quicksetup.jar files I have chosen to minimize the jar files in the class path.

 This way the only files that are not deleted during installation is quicksetup.jar and OpenDS.jar.

8. Improve the wording of the install wizard as proposed by Brian and Neil.

9 . One minor tweak to the QuickSetup Welcome screen: make the reference to the "setup" command a monospace font to highlight it a bit more.

10.  Fix for issue 1057  (stop-ds.bat and start-ds.bat do not work when called using Runtime.exec).  The quicksetup code used to overwrite the environment variables when calling Runtime.exec which made the server not be able to start/stop correctly.

11. Fix some minor bugs with the default focus on some panels.

12. Update the setup scripts to use the java home file if the setup was previously called.

git-svn-id: https://svn.forgerock.org/opendj/trunk@860 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • c5ffec92   Update the Java Web Start, GUI, and CLI setup modes to write a shell script or ... Browse Dir » 
    batch file that can be used to set JAVA_HOME.  Update all of the tools and
administrative scripts provided with OpenDS so that they will use this to set
JAVA_HOME unless it's already set in the user's environment.

OpenDS Issue Number:  1082


git-svn-id: https://svn.forgerock.org/opendj/trunk@856 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     

08 Dec, 2006

2 commits

05 Dec, 2006

1 commit

  • 4b376839   Update the base DN registration process to address a number of issues: ... Browse Dir » 
    - 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
     

30 Nov, 2006

1 commit

  • 28f11fd3   Update the schema backend so that the attributes used to represent schema ... Browse Dir » 
    information are treated correctly according to their definitions.  In
particular, attributeTypes, objectClasses, matchingRules, and ldapSyntaxes are
now properly treated as operational attributes and not returned unless
explicitly requested.  It is possible to override this behavior for backward
compatibility with clients that expect them to always be returned, but this
may be deprecated in the future.

OpenDS Issue Number:  1039


git-svn-id: https://svn.forgerock.org/opendj/trunk@831 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     

29 Nov, 2006

2 commits

26 Nov, 2006

1 commit

  • 3444e903   Update the server configuration so that the GSSAPI SASL mechanism handler is ... Browse Dir » 
    disabled by default.  This will help eliminate an error message on startup for
systems that do not have proper name resolution configured, and it is not
expected that GSSAPI authentication will be widely used among clients.  It may
be manually enabled in environments where GSSAPI authentication is required.

OpenDS Issue Number:  1036


git-svn-id: https://svn.forgerock.org/opendj/trunk@786 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     

21 Nov, 2006

1 commit

20 Nov, 2006

1 commit

19 Nov, 2006

1 commit

17 Nov, 2006

3 commits

  • 1bbde22c   Rename the "setup.sh" script to "setup" and update all references to it to use ... Browse Dir » 
    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
     
  • aa1d841f   The modifications basically do the following: ... Browse Dir » 
    * 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
     
  • 315ee7f8   The synchronization changelog monitoring information has a counter named ... Browse Dir » 
    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
     

15 Nov, 2006

2 commits

  • 990c1532   Update the OID for the ds-pwp-password-policy-dn attribute so that it no longer ... Browse Dir » 
    conflicts with the OID for the ds-cfg-window-size attribute.

OpenDS Issue Number:  1012


git-svn-id: https://svn.forgerock.org/opendj/trunk@728 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • cbfd0c70   Update the password policy implementation to use ds-pwp-password-policy-dn ... Browse Dir » 
    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
     

13 Nov, 2006

3 commits

10 Nov, 2006

2 commits

  • a294922e   Make a number of changes to administrative tools provided with OpenDS. These ... Browse Dir » 
    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
     
  • 3431c6f0   issue 508 ... Browse Dir » 
    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
     

09 Nov, 2006

2 commits

08 Nov, 2006

2 commits

  • 49c58a7a   Make several property updates to administrative shell scripts and batch files: ... Browse Dir » 
    
- 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
     
  • 1bec92c1   Add a missing backup script that was inadvertently removed when all of the ... Browse Dir » 
    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
     

31 Oct, 2006

1 commit

  • f5384b01   Change the flag used to start the server in the foreground from "-nodetach" ... Browse Dir » 
    (with a single dash) to "--nodetach" (with two dashes).  It can also be used as
"-N" with a single dash.  This has the following benefits:

- It is more consistent with our other command-line arguments, and it is
  CLIP compliant.

- It makes it possible for the flag to appear anywhere in the argument list
  rather than just being the first argument.

- It makes it possible to provide this feature on Windows, whereas before it
  was only available on UNIX-based systems.

- On UNIX-based systems, "--nodetach" is now case-insensitive, although it is
  case-sensitive (all lowercase) on Windows systems.  The "-N" alternative is
  always case sensitive.

OpenDS Issue Number:  900


git-svn-id: https://svn.forgerock.org/opendj/trunk@664 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     

30 Oct, 2006

1 commit

29 Oct, 2006

1 commit

28 Oct, 2006

1 commit

  • 618f29aa   fix for issue 893 ... Browse Dir » 
    the batch files just needed a couple of double-quotes

git-svn-id: https://svn.forgerock.org/opendj/trunk@645 41b1ffd8-f28e-4786-ab96-9950f0a78031
    al_xipe
     

27 Oct, 2006

1 commit

  • f93b9d44   Make a number of changes to administrative batch files for Windows systems: ... Browse Dir » 
    - Update the start-ds.bat file so that it starts in the background rather than
  the foreground, and will not exit until the server has actually started.
  Issue #590.

- Update all of the batch files to explicitly set the PATH for better
  consistency and security.  Issue #607.

- Consolidate a lot of the content into _client-script.bat and 
  _server-script.bat files to make the batch files more maintainable.
  Issue #873.


git-svn-id: https://svn.forgerock.org/opendj/trunk@643 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     

25 Oct, 2006

1 commit

  • 474f1eca   Make several changes to administrative shell scripts provided with OpenDS. ... Browse Dir » 
    All of these changes fall under the blanket of issue 882, but are also
associated with a number of individual sub-issues.

The changes include:

- Create new "_client-script.sh" and "_server-script.sh" shell scripts that
  hold the majority of the logic required to launch the client-side and
  server-side tools (Issue #873).

- Explicitly set the PATH, LD_LIBRARY_PATH, and LD_PRELOAD (and the 32-bit and
  64-bit specific variants of LD_LIBRARY_PATH and LD_PRELOAD) to ensure better
  security and more consistent behavior when invoking external commands
  (Issue #607).

- Fix potential problems that could arise if either OpenDS or the Java runtime
  are installed in a path that contains spaces (Issue #820).

- Update the start-ds.sh script so that it always creates a PID file, whether
  running in the foreground or in the background (Issue #859).

- Update the start-ds.sh script so that when running in the background it will
  not exit until it confirms that the server is actually running.  It will also
  display any messages written to standard output/standard error during
  startup (Issue #590).

- Update the stop-ds.sh script so that it can either perform a local stop (via
  kill with the TERM signal) or a remote stop (over LDAP using the shutdown
  task).  If the script is invoked with no arguments and there is a local PID
  file present, then it will be a local stop via kill, and it will wait until
  the server actually has stopped before exiting.  Otherwise it will be a
  remote stop over LDAP (Issue #871).


git-svn-id: https://svn.forgerock.org/opendj/trunk@640 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     

22 Oct, 2006

2 commits

  • 9a22963d   Add the nsUniqueId operational attribute to the OpenDS schema. We don't ... Browse Dir » 
    intend to use it, but it can help provide compatibility with the Sun Java
System Directory Server, as that server includes the nsUniqueId attribute when
performing LDIF exports.

OpenDS Issue Number:  853


git-svn-id: https://svn.forgerock.org/opendj/trunk@629 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • 530b327a   Update the groupOfNames objectclass to make the member attribute optional, and ... Browse Dir » 
    update the groupOfUniqueNames objectclass to make the uniqueMember attribute
optional.  This varies from the standard definition in RFC 4519, but it makes
more sense for them to be optional.  It provides better compatibility with the
Sun Java System Directory Server, and it greatly simplifies problems like how
to handle an attempt to delete a user account if referential integrity is
enabled and that user is the last remaining member in a group.

OpenDS Issue Number:  619


git-svn-id: https://svn.forgerock.org/opendj/trunk@628 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     

14 Oct, 2006

1 commit

13 Oct, 2006

1 commit

20 Sep, 2006

1 commit

  • c606f87c   Add a new password policy for root users to isolate them from changes to the ... Browse Dir » 
    default policy and to make it more obvious that root users are subject to
password policy enforcement.  The new password policy is the same as the
default policy with the following exceptions:

- The default password storage scheme has been changed from SSHA to SSHA512
- There is no default password generator
- Password changes require that the current password be provided

OpenDS Issue Number:  676


git-svn-id: https://svn.forgerock.org/opendj/trunk@397 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     

19 Sep, 2006

1 commit