org.forgerock / org.forgerock.opendj

13 Jun, 2007

1 commit

  • a9fc769d   Add support for tagging managed object definitions so that similar types of mana… ... Browse Dir » 
    …ged object can be grouped together. Tagging will enable us to automatically generate more user-friendly documentation and administration tools as a result of them being easier to navigate and search. For example, an administration CLI will be able to split the available set of sub-commands into categories, thus making it easier for administrators to find the sub-command that they need.

This change is implemented as follows:

* provide an extensible way in which tags can be defined: the XML root configuration definition element now supports an "adm:tag-definition" element, which can be used as follows:

  <adm:tag-definition name="logging">
    <adm:synopsis>Logging</adm:synopsis>
  </adm:tag-definition>

* provide a means for tagging managed object definitions with zero or more tags using an "adm:tag" element, which can be used as follows:

  <adm:tag name="logging"/>

* add support to the admin framework APIs for querying a managed object definition's tags

* define an initial set of tags and tag managed object definitions appropriately (this is just an initial guess and is likely to change):

  * logging
  * replication (incl. mmr)
  * database (incl. caching)
  * security (authn and authz)
  * identity (user account management, pwp, etc)
  * core (connection handlers, virtual attributes, etc)


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

12 Jun, 2007

1 commit

11 Jun, 2007

3 commits

  • 3b0ebacb   Add a CLI profile for defining CLI related annotations to managed object and pro… ... Browse Dir » 
    …perty definitions. The CLI profile defines two annotations at the moment:

* the operand name which should be used in sub-command usage help to identify the names of managed objects being added, removed, modified, etc
* the list of properties which should be displayed by default in list-xxx sub-commands. For example, when listing connection handlers we can display a summary table that lists the "enabled", "listen-port", and "use-ssl" properties by default

Both of these annotations apply only to relation definitions. Existing relations have been updated to include these CLI annotations, although their content is subject to change if we decide that better operand names/default properties exist.

These annotations will be used in the forthcoming dsconfig CLI.

git-svn-id: https://svn.forgerock.org/opendj/trunk@2075 41b1ffd8-f28e-4786-ab96-9950f0a78031
    matthew_swift
     
  • ec4635e7   Add support for specifying a "usage" string for string based property definition… ... Browse Dir » 
    …s which define a pattern constraint. The usage string is used when the syntax of a property needs to be displayed, for example in a CLI help screen or in server-side log messages when a bad property value is encountered. For example, a property whose values must be a valid UNIX mode could have the following string syntax definition:

       <adm:string>
         <adm:pattern>
           <adm:regex>^[0-7][0-7][0-7]$</adm:regex>
           <adm:usage>MODE</adm:usage>
           <adm:synopsis>
             An valid UNIX mode string. The mode string must contain three
             digits between zero and seven.
           </adm:synopsis>
         </adm:pattern>
       </adm:string>

Existing string based properties have been updated with appropriate usage.


git-svn-id: https://svn.forgerock.org/opendj/trunk@2073 41b1ffd8-f28e-4786-ab96-9950f0a78031
    matthew_swift
     
  • e6352e01   Final part for issue 604 : replication needs to resolve naming conflicts ... Browse Dir » 
    These changes are the last part of the naming conflict resolution.
It also introduce the ds-sync-conflict attribute that is used to mark the entries for which
an automatic conflict resolution is not possible. 

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

08 Jun, 2007

3 commits

  • 35e06c6f   This commit address several related issues regarding the upgrader CLI: ... Browse Dir » 
    - After discussing the previously noninteractive option with Brian, I changed the CLI options somewhat.  The new CLI design is to specify an interactive option (if interactivity is desired) rather than to have to specify non-interactivity.  Additionally interactivity is only supposed to apply to gathering of required information and not whether or not and application is allowed to prompt for such things as continuation following an error.  To suppress these sort of prompts you should specify the silent option.  So the common plumbing (currently not used by setup or uninstall) now operates as described above and the upgrader now has a both silent and interactive options as described.

- Make BuildExtractor a Launcher.  BuildExtractor is a simple program used by the CLI for unzipping an OpenDS .zip file.   Previously is was not very smart, relying on the Upgrader to report status and make sure the unzipping went OK.  This had the unfortunate side-effect of making the scripts overly complicated resulting in issue 1772, and made it difficult to support interactivity.  So the BuildExtractor has been made smarter so that it is capable of parsing the complete command line invocation, printing usage, and performing verification that it performed properly.

- Addresses issue 1772 by simplifying and correcting the upgrade and upgrade.bat scripts.



git-svn-id: https://svn.forgerock.org/opendj/trunk@2061 41b1ffd8-f28e-4786-ab96-9950f0a78031
    kenneth_suter
     
  • 93b41b99   Fixed an issue where the error log doesn't actually log messages. Also improved … ... Browse Dir » 
    …the performance of the loggers when they are disabled.

Fixed for issue 1780


git-svn-id: https://svn.forgerock.org/opendj/trunk@2059 41b1ffd8-f28e-4786-ab96-9950f0a78031
    boli
     
  • a07bf0e2   Use the first parameter of the batch file instead of the batch file itself to te… ... Browse Dir » 
    …st whether we use the winlauncher.exe or not for the setup and the uninstall.


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

07 Jun, 2007

4 commits

  • b49fe277   Eliminate the search-unindexed privilege, since the feature was implemented to ... Browse Dir » 
    use a privilege of "unindexed-search" instead.  Also, eliminate the
index-rebuild privilege and fold all of its functionality into ldif-import,
since having a separate privilege for it doesn't provide much benefit and
creates additional administrative overhead.

OpenDS Issue Numbers:  1765, 1776


git-svn-id: https://svn.forgerock.org/opendj/trunk@2051 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • 630ba039   Add a virtual attribute provider that can be used to assign entryUUID values ... Browse Dir » 
    for entries in private backends (e.g., the root DSE, schema, monitor entries,
config entries, etc.).  The entryUUID value that will be generated is based on
an MD5 hash of the entry DN, but this shouldn't be a problem for entries in
private backends because none of them allow modify DN operations.  User entries
should have a real entryUUID value generated when the entry is created (either
via an LDAP add or an LDIF import).

OpenDS Isssue Number:  1775


git-svn-id: https://svn.forgerock.org/opendj/trunk@2050 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • a7b98ade   Update the global ACI definitions to allow all users to read entryUUID. ... Browse Dir » 
    
git-svn-id: https://svn.forgerock.org/opendj/trunk@2048 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • 2872c1cf   Fix for issue 1633 (JMX port should be disabled by default) ... Browse Dir » 
    Considering the limited added value that the JMX port will provide on 1.0 and the fact that we do not want to expose it on the QuickSetup, in the admin group we consider to disable this port by default.  Before committing a fix for this maybe we should send a Heads Up message to the users mailing list.

Basically after the changes the JMX connection handler will not be enabled if the server is installed using the graphical setup.  For the command line setup, JMX will not be enabled unless the user explicitly includes de -x option (for the JMX port) when invoking the command-line.



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

05 Jun, 2007

1 commit

04 Jun, 2007

1 commit

  • 39888924   Fix for issue 1753. ... Browse Dir » 
    Instead of using %* to test if the user provided arguments in the command line just use the first argument with no quotes (%~0) to do the test.  The fix applies both to the setup and the uninstall scripts on Windows.


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

01 Jun, 2007

1 commit

30 May, 2007

2 commits

  • e2107b9b   Add default plugin-class to example-plugin. ... Browse Dir » 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@1977 41b1ffd8-f28e-4786-ab96-9950f0a78031
    matthew_swift
     
  • a49181bf   Fix issue 1736: add default values for java-implementation-class properties ... Browse Dir » 
    This change adds default values for all java-implementation-class style properties where appropriate. These properties are usually defined in an abstract definition but have sensible default values in their sub-definitions. For example, the PasswordValidatorConfiguration definition defines a "validator-class" property which is mandatory but has no sensible default value. However, its derived definition DictionaryPasswordValidatorConfiguration does have a sensible default value for this property, DictionaryPasswordValidator, so this change adds a "property-override" to this sub-definition which defining this default value.

Having default values defined for java-class type properties will make it much easier for administrators to create new configurations as they will no longer need to figure out which class is appropriate (they are still free to override the default with their own implementation if they wish).

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

29 May, 2007

1 commit

  • 4cb23fdd   Fix issue 1580: support overriding of property default values. ... Browse Dir » 
    It is now possible to override the default behavior and required admin action of an inherited property definition using a "property-override" element. This makes it possible to specify default values for inherited properties like java-implementation-class and will, ultimately, make a client tools much more user-friendly.

A subsequent change will add default values for java-implementation-class properties in all managed object definitions.


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

28 May, 2007

1 commit

  • 7b92b893   Fix the following issues: ... Browse Dir » 
    * 1444: implement inherited default values
* 1445: prevent commit if mandatory properties are missing
* 1446: refactor managed object factory method API in generated APIs
* 1625: allow read-only properties to be defined during managed object construction and add support for "monitoring" properties (e.g. a property which is server generated and contains the list of support ciphers)

These issues have been fixed in a single change as they depend upon each (issue 1446 being the main issue).

[Reviewed by Josu]


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

24 May, 2007

1 commit

23 May, 2007

1 commit

22 May, 2007

1 commit

  • f74ef984   Various improvements and refactorings of the admin framework client API, including: ... Browse Dir » 
    * client API methods are much more specific about what sort of exceptions they can throw

* new exceptions for wrapping underlying transport related error conditions (e.g. IO problems, authorization problems)

* improved Javadoc generation for client APIs

* pull-up AbstractPropertyDefinitionVisitor into PropertyDefinitionVisitor and improve type-safety of EnumPropertyDefinition visitor method

* refactor the LDAP client implementation (remove LDAPChangeBuilder, introduce JNDI DirContext wrapper interface called LDAPConnection to make the client APIs more testable)

* move various unit test classes out of the admin server-side unit tests so that they can be re-used by client unit tests

* introduce "mock" client connections and property providers to facilitate testing of the admin client API

* implement client API unit tests


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

18 May, 2007

1 commit

17 May, 2007

1 commit

16 May, 2007

2 commits

15 May, 2007

3 commits

  • f9eaa0eb   Update the way the Java Web Start installer creation script finds the path to ... Browse Dir » 
    the Director Server JAR files to take the new version numbering scheme into
account.


git-svn-id: https://svn.forgerock.org/opendj/trunk@1881 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • 4471d7e4   This commit removes the Web Start version of the upgrader's ability to download … ... Browse Dir » 
    …arbitrary builds to be used for upgrading.  Instead, the Web Start version of upgrade will be tied to the  build version of upgrader.  This is necessary after discovering that attemping to perform internal communication with the directory server when the DS bit and the upgraders bits are of different versions is problematic.

- The Web Start upgrader will now need to be invoked by clicking an 'upgrade to this build' link presumably on the OpenDS website.  We will need to think about how to present this to users.  I've removed the ability of the 'upgrade' script to invoke the WebStart version of the upgrader.  So at least for the time being, the upgrader scripts are CLI only.  At some point it might be possible to have a command execute a GUI version.

- Removed the Choose Version step of the upgrader although I have kept the UI classes for downloading the build in place since I presume this is something we will want to pursue at some point.  It is now easy to determine the current future version of the build (since it matches the upgrader's version) and so the upgrader's Review Page has been fixed to always show the correct version of the build to which the upgrade will be performed.

- InProcessServerController now throws an exception if the current version of OpenDS does not match the version of the installation parameter.

- I have removed the initial pre-flight test that the upgrader was performing on the server before the upgrade.  If you did not know, the upgrader would perform a check and refuse to upgrade a server that spit out error messages when started.  Technically the check would need to be performed external to the JVM and I am not sure that our method for gathering log message spit out by the server is gauranteed to work on all platforms (Windows) and in all cases.  At any rate, Brian though the check was unnecessary so I have disabled it.  The upgrade still cancels if there are errors starting the server after the upgrade has been performed.

- I have re-enabled adding of the upgrade scripts to the build.

- I've updated the usage message for the CLI removing references to the GUI version of the tool as well as suggest visiting opends.org to use the web start version of the tool.

- Externalized the exectution of the backup databases process.


git-svn-id: https://svn.forgerock.org/opendj/trunk@1880 41b1ffd8-f28e-4786-ab96-9950f0a78031
    kenneth_suter
     
  • 5faa3a13   Make a number of administrative types of updates: ... Browse Dir » 
    - Change the way that we construct the server version number.  This is
  explained in detail at
  https://www.opends.org/wiki/page/TheOpenDSVersionNumber

- Remove the CheckEOLStyle and CheckCopyrightDates ant targets and replace them
  with a single CheckPrecommit target that does both tasks and should be much
  more efficient.  This should prevent out of memory errors on some platforms
  that were experiencing them before.

- Update the build process so that Javadoc generation is no longer part of the
  precommit target.  This has been known to take a significant length of time
  and is unlikely to catch many problems that checkstyle doesn't already
  detect.


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

10 May, 2007

1 commit

09 May, 2007

1 commit

08 May, 2007

3 commits

07 May, 2007

2 commits

04 May, 2007

1 commit

  • 0025ece0   Fixes for the 2 replication problems : ... Browse Dir » 
    - Missing cn attribute in replication.ldif


- When at least 2 replication servers are used, they will both try to connect to each other.
Since there must be only one connection, one of the connection is rejected.
Unfortunately in some cases the replication server fails to recognize that they are
already connected and keep trying to connect to the other replication server
every second.

The reason while they fail to notice that they are already connected is because
there is a confusion in the code between the IP address and the hostname.
This fix uses the IP address everywhere and also add checks between the IP address
and the local IP address : 127.0.0.1.





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

03 May, 2007

3 commits

  • 5ec7b4df   Major changes made to the logging framework. It should resolve the following issues: ... Browse Dir » 
    1. Migrated configuration to the new admin framework.
2. Removed all dependencies on the JDK logger. (Issue 1503)
3. Added option to set the file permissions on all log files. (Issue 202)
4. Added option to write log files asynchronously.
5. Retention and rotation policies are now separate managed objects registered to the Directory Server.
6. Rotation and retention policies are not extensible.
6. Post-rotation actions are not yet implemented in this set of changes.
7. Tools and tasks can now use a custom log publisher that only picks up messages generated by a specific thread or thread group.
8. Debug logger no longer creates a log record object for every message. 
9. Configurable Log File Paths (Issue 174)
10. Log Level Support by Category/Severity. This capability is limited for error logger. (Issue 177)
11. Support log file rotation (Issue 188)
12. Sized-based, Time-based rotation policies (Issues 190, 191)
13. Time-based, max size-based, file count-based retention policies (Issues 199, 201, 202)
14. Debug logger configurable via the admin framework (Issue 836)



git-svn-id: https://svn.forgerock.org/opendj/trunk@1805 41b1ffd8-f28e-4786-ab96-9950f0a78031
    boli
     
  • 2606575c   This is a checkin for Issue #311 "CRYPT Storage Scheme Support". This ... Browse Dir » 
    code was contributed externally by java.net user bdamm.

The crypt implementation itself was ported from the C-based one
OpenSolaris.  Since the OpenSolaris code is covered under the CDDL,
we're okay to include it in OpenDS, but I've opened issue 1573 to
remind us to make sure that we got all of the copyrights right etc.


git-svn-id: https://svn.forgerock.org/opendj/trunk@1801 41b1ffd8-f28e-4786-ab96-9950f0a78031
    davidely
     
  • 60cc017b   This update to the script fixes a problem where the script would try to invoke t… ... Browse Dir » 
    …he webstart version of the tool if there were any problems with the command line invocation (incorrect arguments etc).  Now the webstart version will be launched only if there are no arguments passes to the tool.  Otherwise the command line version is used.

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