14 Oct, 2006

1 commit


13 Oct, 2006

1 commit


20 Sep, 2006

1 commit

  • 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


17 Sep, 2006

1 commit


15 Sep, 2006

1 commit

  • directory holding the database files. The new config attribute
    ds-cfg-backend-mode is optional and by default has a value of 700. The
    permissions are set on backend initialization as well as on the fly via
    LDAP. The server will make sure the file permissions will allow owner
    access before setting. Any exceptions encountered while setting the
    attribute will result in non fatal errors which are logged. However, any
    configuration exceptions will keep the backend from starting.
    
    Fix for issue 50
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@353 41b1ffd8-f28e-4786-ab96-9950f0a78031
    boli
     

07 Sep, 2006

1 commit

  • in an LDIF file rather than over LDAP.  There are some limitations, including:
    
    - Modify DN operations are not supported
    - Operations that would attempt to delete or alter an entry after adding it
    
    Also, this capability has been integrated into the Directory Server startup
    process so that it is now possible to have a config/config-changes.ldif that
    will automatically be applied to the config/config.ldif file before it gets
    processed by the server.  This makes it easy to make configuration changes with
    the server offline without directly altering the configuration file, and can be
    used to make changes to the configuration needed for running test cases.
    
    OpenDS Issue Numbers:  622, 623
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@298 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     

01 Sep, 2006

1 commit


31 Aug, 2006

3 commits


24 Aug, 2006

1 commit

  • …or matches during a search operation. A value of -1 or 0 will remove the limit, like the behavior of DS 5 and 6. Changed the "unlimited" values of size and time limits to be consistent with the lookthrough limit (-1 or 0). 
    
    - It adds a new server wide config attribute (ds-cfg-lookthrough-limit)
    with default of 5000
    
    - It adds a new operational attribute (ds-rlim-lookthrough-limit) so
    that a user's entry can be checked for a custom lookthrough limit on
    bind for per user configurations.
    
    - cn=Directory Manager by default will not have a lookthrough limit
    
    Fix for issue 52
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@201 41b1ffd8-f28e-4786-ab96-9950f0a78031
    boli
     

23 Aug, 2006

1 commit

  • initializes...." message at the beginning of the process which can make any
    delays introduced by the initial configuration and schema processing more
    palatable to the end user.
    
    This also updates the setup.sh shell script so that it will attempt to use the
    client VM under certain circumstances, since we have found that the client VM
    does significantly reduce the startup time in many cases.  It should continue
    to work properly in other VMs that may not support the "-client" option.
    
    OpenDS Issue Number:  594
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@197 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     

19 Aug, 2006

1 commit

  • - Add a --quiet option to the import utility, which allows it to run without
      any output.
    
    - Update the setup utility to use the import quiet mode when creating the base
      entry.
    
    - Make sure that all messages written by the setup utility will be properly
      wrapped to be better suited for 80-column displays.
    
    - Remove the return statements from the setup process for the case in which it
      cannot bind to the requested port.  This will cause it to loop and allow the
      user to choose a different port.
    
    - Update the setup script and batch file to provide the program name argument.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@190 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     

18 Aug, 2006

1 commit


16 Aug, 2006

1 commit


15 Aug, 2006

1 commit


14 Aug, 2006

1 commit

  • - Update the account status notification type structure to include the DN of
      the associated user.
    
    - Update the bind processing code to generate account status notifications for
      the following conditions:
      * Bind failed due to an expired account
      * Bind failed due to a reset-locked account
      * Bind failed due to an idle-locked account
      * Bind failed due to an expired password
      * The first time a password expiration warning is generated
      * If the bind failure count limit is reached and the account becomes locked
    
    - An error log account status notification handler has been added, which can
      write messages to the error log when an account status notification is
      generated.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@162 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     

10 Aug, 2006

1 commit


04 Aug, 2006

2 commits


02 Aug, 2006

1 commit

  • possible for accounts to be given an expiration time, after which it will not
    be possible to authenticate as that user or target that user with the proxied
    authorization control.
    
    If the ds-pwp-account-expiration-time operational attribute is included in the
    user's entry and it references a time in the past, then the user's account will
    be considered expired.  If it references a time in the future, then it will be
    expired at that time.  If this attribute is absent, then the account will not
    expire.
    
    OpenDS Issue Number:  543
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@131 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     

24 Jul, 2006

3 commits

  • in the server.  Also create a very simple README that will also be included.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@31 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • - put changelog configuration below cn=Multimaster Synchronization,cn=Synchronization Providers,cn=config
    - use ds-cfg-changelog-server-id and ds-cfg-directory-server-id instead of ds-cfg-server-id
    - don't require the ds-cfg-changelog-server attribute in changelog configuration (ds-cfg-synchronization-changelog-server-config objectclass)
    
    Use dc=example,dc=com instead of dc=com in he synchronization configuration example
    
    improve the javadoc
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@30 41b1ffd8-f28e-4786-ab96-9950f0a78031
    gbellato
     
  • cn=MultimasterSynchronization,cn=Synchronization Providers,cn=config
    to 
    cn=Multimaster Synchronization,cn=Synchronization Providers,cn=config
    
    (notice the whitespace between Multimaster and Synchronization)
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@27 41b1ffd8-f28e-4786-ab96-9950f0a78031
    gbellato
     

23 Jul, 2006

1 commit


22 Jul, 2006

1 commit


18 Jul, 2006

1 commit

  • lock timeout attribute to use an integer with unit syntax rather than just an
    integer.
    
    Also, update the FIFO entry cache implementation to get rid of the calls to run
    the garbage collector.  Instead, if we detect that too much memory is being
    used, we'll not store the new entry and get rid of an old entry.  This is much
    more palatable in terms of performance and response time when the cache gets
    full.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@19 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     

16 Jul, 2006

1 commit


28 Jun, 2006

1 commit