02 Mar, 2007

13 commits


01 Mar, 2007

12 commits


28 Feb, 2007

10 commits

  • should be presented based on its alias (aka its nickname).  This is used both
    by server-side code which needs to present a certificate to clients, as well as
    by client-side code which needs to present a certificate to the server.
    
    OpenDS Issue Number:  1292
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@1279 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • git-svn-id: https://svn.forgerock.org/opendj/trunk@1278 41b1ffd8-f28e-4786-ab96-9950f0a78031
    kenneth_suter
     
  • PasswordPolicy.requireSecureAuthentication (via PasswordPolicyState.getPolicy).
    I had missed this call in an earlier commit.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@1277 41b1ffd8-f28e-4786-ab96-9950f0a78031
    david_page
     
  • PasswordPolicy.requireSecureAuthentication (via PasswordPolicyState.getPolicy). I had missed this call in an earlier commit.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@1276 41b1ffd8-f28e-4786-ab96-9950f0a78031
    david_page
     
  • configuring synchronization for suffix cn=schema (issue 613) .
    
    You may want to read the schema Synchronization documents before reviewing this
    https://opends.dev.java.net/public/docs/dev-docs/SchemaSyncFeatureRequirements.html   and
    https://opends.dev.java.net/public/docs/dev-docs/SchemaSyncDesign.html
    
    It includes :
    
    - Change the PersistentServerState to use attribute ds-sync-state in the base entry
     instead of a specific entry.
     Add new unit test for the PersistentServerState class.
     Change attribute ds-sync-state to be an operational attribute.
    
    - Change the schema backend to allow storage of the ds-synch-state attribute in the
     schema ldif File.
     This change is arguable because  I have chosen to make this as simple as possible
     and therefore only allowed the storage of this attribute in the schema File.
     While this has the advantage of being very simple it has
     the drawback of adding some code in the schema backend that is only related to synchronization.
     The other choice would be to add a generic service in the schema backend for storing
     any type of attribute.
     Please tell me if you think that this would be better.
    
    - Disable the conflict resolution for cn=schema so that we don't polute the ldif entries
     with the historical information
    
    - Add unit test for schema synchronization
    
    The work for schema synchronization is not complete with this.
    A second round of modification is necessary for synchronizing the schema changes
    done by manually editing the files or by dynamically loading a file.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@1275 41b1ffd8-f28e-4786-ab96-9950f0a78031
    gbellato
     
  • This change makes possible to configure the Changelog purge delay that
    was previously hard-coded using the ds-cfg-changelog-purge-delay attribute.
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@1274 41b1ffd8-f28e-4786-ab96-9950f0a78031
    gbellato
     
  • 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@1273 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • The problem was caused because in the class InstallDS the check for the port was not performed when the user already provided the port through the command line (see first diffs in InstallDS).
    
    The rest of the diffs consist of factorization of code to be shared between the quicksetup classes and the class org.opends.server.tools.InstallDS.  Some methods from the Utils class of quicksetup have been moved to the SetupUtils class; these methods allow to know if a given port is priviledged or not, if we can use it to configure the server and to know in which Operating System the JVM is running.   The operating system methods use the enumeration OperatingSystem (which has been slightly modified to not have dependencies on other classes and to be included in quicksetup.jar).
    
    Extra: use the class LockFileManager to know if the server is running or not.  The use of this class does not impact the Web Start Installer as we only want to know if the server is running or not once we have tried to start it (and so OpenDS.jar has already been loaded by the class loader).
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@1272 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • draft-wahl-ldap-session and the new draft-zeilenga-sasl-yap document.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@1270 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • . run the functional tests on windows
      . download the daily build and install it to run the functional tests
      . gather test coverage by editing the package on the fly to launch emma
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@1269 41b1ffd8-f28e-4786-ab96-9950f0a78031
    al_xipe
     

27 Feb, 2007

4 commits

  • 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@1267 41b1ffd8-f28e-4786-ab96-9950f0a78031
    el_kaboing
     
  • 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@1265 41b1ffd8-f28e-4786-ab96-9950f0a78031
    el_kaboing
     
  • Neil for issue #1266:  use a hidden option to check whether the server
    is already running or not.  If the server is not running the message
    'Server already stopped' is displayed, if the server is running the message 'Stopping Server... is displayed'.
    
    So the output of the command with this changes is:
    
    If the server is running
    ========================
    
    bash-3.00$ bin/stop-ds --restart
    Stopping Server...
    
    [23/Feb/2007:17:00:28 +0100] category=CORE severity=NOTICE id=458886
    msg="OpenDS Directory Server 0.1.0 starting up."
    [23/Feb/2007:17:00:34 +0100] category=BACKEND severity=NOTICE id=8847402
    msg="A database backend containing 1 entries has started."
    [23/Feb/2007:17:00:34 +0100] category=CONFIG severity=SEVERE_WARNING
    id=3277325 msg="Access control has been disabled."
    [23/Feb/2007:17:00:35 +0100] category=CORE severity=NOTICE id=458887
    msg="The Directory Server has started successfully."
    [23/Feb/2007:17:00:35 +0100] category=CORE severity=NOTICE id=458891
    msg="The Directory Server has sent an alert notification generated by
    class org.opends.server.core.DirectoryServer (alert type
    org.opends.server.DirectoryServerStarted, alert ID 458887):  The
    Directory Server has started successfully.."
    bash-3.00$
    bash-3.00$ bin/stop-ds
    
    
    
    If the server is stopped
    ========================
    
    bash-3.00$ bin/stop-ds
    Server already stopped.
    bash-3.00$ bin/stop-ds --restart
    Server already stopped.
    [23/Feb/2007:16:59:50 +0100] category=CORE severity=NOTICE id=458886
    msg="OpenDS Directory Server 0.1.0 starting up."
    [23/Feb/2007:16:59:55 +0100] category=BACKEND severity=NOTICE id=8847402
    msg="A database backend containing 1 entries has started."
    [23/Feb/2007:16:59:56 +0100] category=CONFIG severity=SEVERE_WARNING
    id=3277325 msg="Access control has been disabled."
    [23/Feb/2007:16:59:57 +0100] category=CORE severity=NOTICE id=458887
    msg="The Directory Server has started successfully."
    [23/Feb/2007:16:59:57 +0100] category=CORE severity=NOTICE id=458891
    msg="The Directory Server has sent an alert notification generated by
    class org.opends.server.core.DirectoryServer (alert type
    org.opends.server.DirectoryServerStarted, alert ID 458887):  The
    Directory Server has started successfully.." 
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@1263 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • the new certificate mappers, as well as the ds-cfg-changelog-purge-delay
    attribute.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@1262 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     

26 Feb, 2007

1 commit