29 Jun, 2007

1 commit

  • Update the usage to use 'c' as a short option for 'cli' instead of 'i'.
    
    Update the code to accept the short argument for cli.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2218 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     

28 Jun, 2007

13 commits


27 Jun, 2007

6 commits

  • state information for a user, including getting and setting various state
    variables (even those marked NO-USER-MODIFICATION, although these are typically
    intended for testing purposes only).  Users will be required to have the
    password-reset privilege in order to be able to use this extended operation,
    and access control will also come into play.
    
    Also, include a manage-account tool that can be used to interact with this
    extended operation.  It supports a subset of the capabilities made available in
    the extended operation (e.g., it only allows one operation per use, whereas the
    extended operation allows you to include multiple operations), and some of the
    features intended for testing purposes are marked hidden so that they aren't
    readily apparent to end users.
    
    Finally, fix a bug in which it was not possible for users to authenticate if
    their account had the pwdReset flag and last login time tracking was enabled.
    
    OpenDS Issue Numbers:  292, 579, 1782, 1845
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2201 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • this commit is for hidden subcommand
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2196 41b1ffd8-f28e-4786-ab96-9950f0a78031
    lutoff
     
  • …hod.  In addition it includes a mechanism for running Windows specific tests
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2194 41b1ffd8-f28e-4786-ab96-9950f0a78031
    kenneth_suter
     
  • GROUP_ID and MEMBER_ID operand are now respectively replaced by arguments:
     * -g, --groupName {group-name}
     * -m, --memberName {member-name}
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2193 41b1ffd8-f28e-4786-ab96-9950f0a78031
    lutoff
     
  • git-svn-id: https://svn.forgerock.org/opendj/trunk@2192 41b1ffd8-f28e-4786-ab96-9950f0a78031
    lutoff
     
  • git-svn-id: https://svn.forgerock.org/opendj/trunk@2191 41b1ffd8-f28e-4786-ab96-9950f0a78031
    kenneth_suter
     

26 Jun, 2007

6 commits

  • …n changes made to the server using an internal connection where not persisted in the config.ldif file.  The problem appears to have been an unclosed stream that was preventing the renaming of config.ldif.tmp to config.ldif.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2190 41b1ffd8-f28e-4786-ab96-9950f0a78031
    kenneth_suter
     
  • git-svn-id: https://svn.forgerock.org/opendj/trunk@2189 41b1ffd8-f28e-4786-ab96-9950f0a78031
    kenneth_suter
     
  • an LDIF import.  The basic practice is as follows:
    
    - If the entry specifies a particular password policy, then the default
      password storage schemes for that policy will be used to encode the password.
    
    - If the entry does not specify a particular password policy, then the server
      will use the password scheme(s) specified in the
      ds-cfg-default-user-password-storage-scheme or
      ds-cfg-default-auth-password-storage-scheme attribute in the plugin
      configuration entry, if they are present.
    
    - If the configuration entry does not specify a default set of storage
      schemes, but it uses a password attribute that has the same syntax as the
      password attribute used by the server's default password policy, then the
      default password storage schemes from the server's default password policy
      will be used.
    
    - If all else fails, the server will use SSHA for passwords with the user
      password syntax, or SHA1 for passwords with the auth password syntax.
    
    OpenDS Issue Number:  849
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2186 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • git-svn-id: https://svn.forgerock.org/opendj/trunk@2182 41b1ffd8-f28e-4786-ab96-9950f0a78031
    lutoff
     
  • git-svn-id: https://svn.forgerock.org/opendj/trunk@2181 41b1ffd8-f28e-4786-ab96-9950f0a78031
    lutoff
     
  • the behavior of the server when replication has been configured but the
    replication have not been able to connect to any of the configured replication server.
    
    This configuration attribute is named stays in the replication domain
    configuration entry and is named : ds-cfg-isolation-policy
    
    The possible behavior values are :
    - reject-all-updates : When this value is used and the server cannot connect to
     any of the replication server, all the updates are rejected with an
     UNWILLING TO PERFORM error code.
     This is the default value
    - accept-all-updates :  When this value is used and the server cannot connect to
     any of the replication server, all the updates are accepted without sending them to
     a replication server, when a replication server  will become available, the server will
     use the historical information to generate replication messages.
     This last mode will make the changes at risk because they will only be saved in
     the historical information of the local server. It may also introduce high replication
     delay when the connection establish again.
     Note that currently the replication code is not yet able to generate messages for the
     MODDN, DELETE and ADD operations. (issue 1752)
    
    This change also improve the error messages that are logged when the server cannot connect
    any replication : before the server was continuously logging messages twice per seconds, now
    the server only logs the error the first time and log a new message indicating that everything is
    fine when a replication server is back.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2176 41b1ffd8-f28e-4786-ab96-9950f0a78031
    gbellato
     

25 Jun, 2007

4 commits


24 Jun, 2007

4 commits


23 Jun, 2007

2 commits

  • 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2158 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • implementation is similar to that used by DSEE 6.  The "cn=Plugins,cn=config"
    configuration entry now supports a number of new configuration attributes
    (one per plugin type) that can be used to control the invocation order for
    plugins of that type.  The plugin order specification should be a string that
    is a comma-delimited list of the names of the plugins in the order in which
    they should be invoked, and it should also include an asterisk to indicate
    the order in which any unmatched plugins should be invoked.
    
    For example:
    
         ds-cfg-plugin-order-pre-operation-add: Entry UUID, *
    
    This indicates that the "Entry UUID" plugin should be invoked before any other
    pre-operation add plugins.
    
    The plugin order is evaluated only at startup, and any problems or
    inconsistencies detected (e.g., the same plugin name listed twice in the order,
    or a plugin order that does not contain a wildcard character) will generate
    warning messages in the server's error log.
    
    OpenDS Issue Number:  253
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2157 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     

22 Jun, 2007

4 commits