03 Mar, 2008

1 commit


29 Feb, 2008

1 commit


15 Feb, 2008

1 commit

  • The code has been modified (with no new arguments) in order to work in a best-effort mode.  If the user does not provide authentication we will display the same information independently of whether the server is running or not.  We still display the messages informing that authentication is required to display some monitoring data.
    
    The status panel code has also been updated to have the same behavior.
    
    However it will be required anyhow to provide authentication to display monitoring information since this information is available only through LDAP.
    
    In addition to this changes the following issues have been fixed:
    
    1. Close the ManagementContext created by the LDAPConsoleInteraction object so that we have only one open connection to the server.
    2. Fix a bug when the user chose to accept automatically certificates (the default trust manager was used in this case and we could not connect).
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@3893 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     

13 Feb, 2008

6 commits


12 Feb, 2008

5 commits


11 Feb, 2008

1 commit

  • The fix consists on changing the placeHolderValue from a String to a Message so that it can be localized.  The interfaces and constructors of the argument objects have been updated to reflect this change. The placeholders are defined in tool.properties.
    
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@3853 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     

05 Feb, 2008

1 commit


01 Feb, 2008

2 commits


30 Jan, 2008

2 commits


29 Jan, 2008

2 commits

  • The changes consist basically in using the new attributes
    "approx-older-change-not-synchronized-millis" and "missing-changes" in status and replication status command-lines.  In fact a millisecond version of approx-older-change-not-synchronized-millis has been added in order the remote command-line to be able to provide a localized version of the date (instead of directly presenting the date that was written by the server).
    
    The code has been updated to take into consideration the fact that there is information for several servers; so the replication domain id is used to discriminate the information of the different servers.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@3786 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • Marking revision 3708 as a flag day.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@3785 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     

28 Jan, 2008

2 commits


25 Jan, 2008

3 commits


24 Jan, 2008

5 commits

  • …tup menu leads to corrupted config
    
    Do not allow empty DNs as Directory Manager DN nor as base DNs.  Appart from that an infinite loop has been fixed when the user provided a badly formed DN in the command-line.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@3746 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • …ad will now handle exceptions rasied during rotation and/or retention runs.
    
    Partial fix for issue 2353
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@3745 41b1ffd8-f28e-4786-ab96-9950f0a78031
    boli
     
  • git-svn-id: https://svn.forgerock.org/opendj/trunk@3741 41b1ffd8-f28e-4786-ab96-9950f0a78031
    lutoff
     
  • CertificateMapper should allow a configuration even though there is no 
    quality index defined for the subject-attribute-mapping attribute.
    A severe warning is now logged into the error log.
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@3738 41b1ffd8-f28e-4786-ab96-9950f0a78031
    lutoff
     
  • …ild 6.  The following changes address the issue.  The main thing that has been updated are the changes at the end of VersionCompatibilityIssue.  The problem is that the code relied only on the fact that a flag day was known (we register the flag days).  However it can happen (as it is the case) that a flag day is registered in the code way after the changes occurred.  So when we registered a flag day, systematically we could not upgrade from previous builds.
    
    For instance: a flag day corresponding to build 6 is registered now (candidate build 11). Without these modifications this would prevent to upgrade from build 7 or build 8 to the current build.  That is why the new code actually checks the revision corresponding to the flag day and the revision of the new build.  If the new build is newer than the revision of the flag day then we consider that there is no problem and we continue with the upgrade.
    
    
    
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@3737 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     

23 Jan, 2008

1 commit


22 Jan, 2008

3 commits


21 Jan, 2008

1 commit

  • Change local DB backend configuration so that db-directory and import-temp-directory properties now name a parent directory within which a sub-directory is created having the same name as the backend-id. This simplifies configuration and reduces the risk of name collisions.
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@3708 41b1ffd8-f28e-4786-ab96-9950f0a78031
    matthew_swift
     

18 Jan, 2008

3 commits