30 Aug, 2007

4 commits

  • Also 2094 problem is mostly due to a bad configuration, this fix makes sure
    that the exception happening at the database level is correctly taken
    into account to update the task status.
    
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2861 41b1ffd8-f28e-4786-ab96-9950f0a78031
    gbellato
     
  • The delete-xxx sub-command was silently failing in non-interactive mode because it was silently prompting for confirmation and defaulting to "no". This change also re-enables the file system entry cache unit tests which were failing as a result of this bug.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2860 41b1ffd8-f28e-4786-ab96-9950f0a78031
    matthew_swift
     
  • Modifications done in dsframework CLI are:
    
    1) create-admin-user and set-admin-user-properties are now handled
    privilege properties (--set privilege:[-]<privilege-name>)
    
    2) get-admin-user-properties shows privileges property associated to the
    user 
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2859 41b1ffd8-f28e-4786-ab96-9950f0a78031
    lutoff
     
  • ServerDescriptor#createStandalone now induces the server to initialize its local instance key.
    ADSContext#registerServer writes the instance public-key certificate to "cn=instance keys,cn=admin data" and links that entry to the server entry in ADS.
    
    Still to consider:
    ADSContext#updateServer
    ADSContext#unregisterServer
    ServerDescriptor#setAdsProperties
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2858 41b1ffd8-f28e-4786-ab96-9950f0a78031
    david_page
     

29 Aug, 2007

22 commits


28 Aug, 2007

12 commits

  • 1. replace getNewServerAdsProperties(getUserData()) with ServerDescriptor to:
    a. align with new ReplicationCliMain
    b. allow implementing publicKeyCertificate entry independent of CLI/GUI.
    
    2. inline getRemoteServerProperties (single caller)
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2835 41b1ffd8-f28e-4786-ab96-9950f0a78031
    david_page
     
  • Instead of closing the environment, deleting the files, and re-opening the
    environment, we are keeping the environment open and just truncating the
    databases.  This dramatically reduces the amount of memory required to run the
    unit tests, apparently as a result of a memory leak in the Berkeley DB JE when
    the environment is repeatedly opened and closed.
    
    Note that the latest release of Berkeley DB JE (3.2.44, which we aren't yet
    using) claims to have a fix for a similar problem (JE issue #15444 as described
    in http://forums.oracle.com/forums/thread.jspa?messageID=1782659) but testing
    with that JE version didn't appear to resolve the problem so it is likely that
    the issue still exists.  However, while it was causing a significant problem in
    our test cases, it is unlikely to cause problems in production environments
    because the JE environment should not be repeatedly opened and closed in the
    same JVM instance.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2834 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • …ng TestNG on some machines.
    
    
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2833 41b1ffd8-f28e-4786-ab96-9950f0a78031
    boli
     
  • Clean up duplicate code in Installer.updateADS in preparation for adding instance public-key certificate to properties. External behavior (e.g., registeredNewServerOnRemote) should be unchanged.
    
    Ran precommit tests and various setup hand tests.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2832 41b1ffd8-f28e-4786-ab96-9950f0a78031
    david_page
     
  • git-svn-id: https://svn.forgerock.org/opendj/trunk@2831 41b1ffd8-f28e-4786-ab96-9950f0a78031
    coulbeck
     
  • git-svn-id: https://svn.forgerock.org/opendj/trunk@2830 41b1ffd8-f28e-4786-ab96-9950f0a78031
    coulbeck
     
  • There is a new backend representing the certificate trust store, which allows the setup code to query and populate the trust store over protocol. However, we are using blind trust until that piece of the setup code is ready.
    
    The encryption settings are currently global to the server instance in a new crypto manager config entry. Authentication will always be performed so the main setting is whether to use encryption or not. In the future (post 1.0) we will need to allow encryption to be configured on or off depending on which replication server we are connecting to but we need some discussion on the best way to specify that in configuration.
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2829 41b1ffd8-f28e-4786-ab96-9950f0a78031
    coulbeck
     
  • git-svn-id: https://svn.forgerock.org/opendj/trunk@2828 41b1ffd8-f28e-4786-ab96-9950f0a78031
    coulbeck
     
  • Update the function that created the Message to be displayed to return a String instead of a Message object.
    
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2827 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • git-svn-id: https://svn.forgerock.org/opendj/trunk@2826 41b1ffd8-f28e-4786-ab96-9950f0a78031
    lutoff
     
  • 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2825 41b1ffd8-f28e-4786-ab96-9950f0a78031
    matthew_swift
     
  • send e-mail messages whenever an account status notification is generated.  The
    message can be sent to the end user impacted by the notification (based on an
    attribute in the user's entry) and/or a fixed set of recipients.
    
    The messages that will be generated are created from template files, which can
    include tokens that will be replced with things like:
    
    - The name of the notification type
    - The notification message
    - The DN of the target user's entry
    - Attribute values from the target user's entry
    - Values of account status notification properties, which may vary based on the
      type of notification
    
    This change also includes a fix for a problem that could allow password
    expiration warning messages to be sent to a client even if the bind was not
    successful.
    
    
    OpenDS Issue Number:  581
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2824 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     

27 Aug, 2007

2 commits

  • git-svn-id: https://svn.forgerock.org/opendj/trunk@2823 41b1ffd8-f28e-4786-ab96-9950f0a78031
    al_xipe
     
  • 2 - fix in runTestJob: removed copy of results.html in tmp folder
    3 - fix in staf-installer.xml removed references to results.html
        only rely on my-report.html now
    4 - attach my-report.html to the in place of results.html
    5 - added knowIssue facility to allow to tag tests failing because of known issues
    6 - updated the XSL style sheet to show known issue
    7 - added testcase coloring based on status pass/fail/unknown/known
    8 - added table of contents title row to make it easier for newcomers to read the
        report
    9 - added known bugs calls in backends group
    10- added known bugs calls in security group
    11- added known bugs call in logging group
    12- fix in utils for default windows environment variables
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2822 41b1ffd8-f28e-4786-ab96-9950f0a78031
    al_xipe