09 Aug, 2007

4 commits


08 Aug, 2007

3 commits

  • There are now variants of the isMember methods that include an additional
    Set<DN> argument to which the current group's DN should be added whenever a
    check is made to determine whether a user is a member.  This will help provide
    a mechanism for avoiding infinite recursion loops if two groups both reference
    each other as nested groups.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2594 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • git-svn-id: https://svn.forgerock.org/opendj/trunk@2592 41b1ffd8-f28e-4786-ab96-9950f0a78031
    kenneth_suter
     
  • …ements. These identifiers pave the way for the network group and workflow configuration.
    
    A workflow that is registered with a network group must have an identifier that is not already registered with the network group. To deregister a workflow one has to provide either a workflow base DN or a workflow identifier. The former method is used when a backend is deregistered with the server while the later may be used when applying workflow configuration changes.
    
    The unit-tests are updated accordingly.
    
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2590 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jdemendi
     

07 Aug, 2007

8 commits

  • group implementation.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2589 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2588 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • The following modifications have the following goals:
    
    1. Provide a fix for the GUI part of issue 1894 (consider replication in uninstall).  Basically the graphical uninstall checks whether there is an ADS defined and if the server is configured for replication and asks the users whether (s)he wants to remove the references to the server that is being uninstalled.
    
    2. Fix some minor issues that appear in the merged version of the installer and upgrader.
    
    3. Update the build so that statuspanel.jar disappears.  The idea is to minimize the number of jars that we have.  This is a requirement coming from customers and approved by Neil in a conversation we had a while ago.
    
    4. Minimize the number of classes that go to quicksetup.jar so that its size is the minimal possible and we reduce the download time when launching the WebStart based tools.  This has been done by moving the uninstaller tool to OpenDS.jar (with the status tools). 
    
    
    
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2587 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • 1. Provide a fix for the GUI part of issue 1894 (consider replication in uninstall).  Basically the graphical uninstall checks whether there is an ADS defined and if the server is configured for replication and asks the users whether (s)he wants to remove the references to the server that is being uninstalled.
    
    2. Fix some minor issues that appear in the merged version of the installer and upgrader.
    
    3. Update the build so that statuspanel.jar disappears.  The idea is to minimize the number of jars that we have.  This is a requirement coming from customers and approved by Neil in a conversation we had a while ago.
    
    4. Minimize the number of classes that go to quicksetup.jar so that its size is the minimal possible and we reduce the download time when launching the WebStart based tools.  This has been done by moving the uninstaller tool to OpenDS.jar (with the status tools). 
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2586 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • take some action whenever a subordinate entry is modified as a result of a
    modify DN operation that targets an entry that has one or more children (i.e.,
    a subtree move or subtree rename operation).  At present, subordinate modify DN
    plugins are not allowed to change the contents of the entry as it is being
    moved/renamed, but an appropriate API is in place if we decide to add this
    functionality in the future.
    
    This commit also includes a significant amount of cleanup for plugin result
    code, including corrections to copy-and-paste errors in the javadoc
    documentation.
    
    OpenDS Issue Number:  752
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2584 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • …rader and the installer (which is not yet public).
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2582 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • … and mark the naming property (debug-scope) as read-only. Also fix some minor typos in the descriptions.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2581 41b1ffd8-f28e-4786-ab96-9950f0a78031
    matthew_swift
     
  • git-svn-id: https://svn.forgerock.org/opendj/trunk@2580 41b1ffd8-f28e-4786-ab96-9950f0a78031
    matthew_swift
     

05 Aug, 2007

2 commits

  • 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2571 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • Mark the panels as non opaque to avoid having the white box in certain windows environments.
    
    Instead of simulating a click on the OK button when the user accepts the certificate, directly call the method invoked when the button is clicked.  This avoids having issues with focus, that actually make the button click to be ignored.
    
    Use hexadecimal representation of the certificate instead of the address of the byte array.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2570 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     

04 Aug, 2007

1 commit


02 Aug, 2007

3 commits


01 Aug, 2007

5 commits

  • Fixed issue 2045. The import will delete the database files if only one base DN is used with the backend being imported instead of calling the 
    JE clear method.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2544 41b1ffd8-f28e-4786-ab96-9950f0a78031
    boli
     
  • encoded.  It was previously thought to have no value, but in actuality it
    should have always have a value whose string representation should be "0".
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2542 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • git-svn-id: https://svn.forgerock.org/opendj/trunk@2541 41b1ffd8-f28e-4786-ab96-9950f0a78031
    lutoff
     
  • Modifications done in dsframework CLI are:
          - implement subcommand for global admin user management inside
            the admin registry
    
    The dsframework help output is in attachment in addition to the svndiff
    file and new added file.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2540 41b1ffd8-f28e-4786-ab96-9950f0a78031
    lutoff
     
  • may be returned to a client. Smart referral entries contain the referral objectclass and
    have one or more "ref" attributes containing LDAP URLS. The ref attribute type has usage
    distributedOperation, so the operational shorthand '+' character can be used to match it:
    
    (targetattr="+")(version 3.0; acl "ref wild-card"; allow(read) userdn="ldap:///anyone";)
    
    or it can be explicitly used:
    
    (targetattr="ref")(version 3.0; acl "ref"; allow(read) userdn="ldap:///anyone";)
    
    It is also possible to add an ACI on the referral entry itself:
    
    dn: uid=smart, ou=People, dc=example, dc=com
    objectclass: top
    objectClass: extensibleobject
    objectClass: referral
    ref: ldap://kansashost/OU=People,O=Kansas,C=US
    ref: ldap://texashost/OU=People,O=Texas,C=US
    aci: (targetattr = "ref")(version 3.0; acl "add_aci"; allow (read) userdn="ldap://anyone";)
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2539 41b1ffd8-f28e-4786-ab96-9950f0a78031
    dugan
     

31 Jul, 2007

5 commits

  • - Added the ability to use both a backend ID and include branch arguments for LDIF imports 
    (Issue 1971)
    - Fixed incorrect search scope enum in the VLV index configuration
    - Added unit tests for partial LDIF imports
    - Fixed issue where using overlapping include branches during an import would result in a ConcurrentModificationException (Issue 2039)
    
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2538 41b1ffd8-f28e-4786-ab96-9950f0a78031
    boli
     
  • the password expiration warning interval must always be less than the maximum
    password age.  This ensures that the minimum password age will itself always be
    less than the maximum age, and will also prevent a scenario in which the user
    could receive password expiration warning messages during a period when he/she
    cannot change the password due to the minimum age.
    
    OpenDS Issue Number:  2032
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2535 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • …ssages. Any argument name references are now double-quoted and always preceded by a dash or double-dash as appropriate. This is to avoid potential ambiguity in some error messages and to also be consistent.
    
    Fixes issue 2000.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2534 41b1ffd8-f28e-4786-ab96-9950f0a78031
    matthew_swift
     
  • Make the list-properties sub-command more consistent with the rest of dsconfig. Rather than display the full component name in the left hand column, dsconfig now splits the name into two columns: the first being the generic component name and the second containing the sub-type name. For example, previously an LDAP connection handler would have the component name "ldap-connection-handler". Now the name is split in two using the generic name "connection-handler" and the sub-type "ldap". This is consistent with the create-xxx sub-commands, where the generic name is typically the sub-command suffix (e.g. create-connection-handler) and the sub-type is the value of the -t flag (e.g. ldap).
    
    To make the sub-command more usable, it now has the following three additional options:
    
    -c, --category {CATEGORY}
        The category of components whose properties should be described
    -t, --type {TYPE}
        The type of components whose properties should be described. The value for
        TYPE must be one of the component types associated with the CATEGORY
        specified using the "--category" option
    --inherited
        Modifies the display output to show the inherited properties of components
    
    The CATEGORY can be either a generic component name (e.g. backend or connection-handler), or it can be one of the --help-xxx categories (e.g. logging). The TYPE, if specified, must be a sub-type associated with the specified CATEGORY (e.g. ldap or jmx for connection handlers). The option "inherited" forces the sub-command to display all the properties associated with each component type, including inherited properties.
    
    All the options are optional (e.g. the -t option does not require the -c option).
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2533 41b1ffd8-f28e-4786-ab96-9950f0a78031
    matthew_swift
     
  • git-svn-id: https://svn.forgerock.org/opendj/trunk@2532 41b1ffd8-f28e-4786-ab96-9950f0a78031
    lutoff
     

30 Jul, 2007

9 commits

  • notify administrators whenever a given task has been completed.  It is possible
    to specify a set of administrators that should be notified only if the task
    does not complete successfully, and/or a set of administrators that should be
    notified regardless of the task's success or failure.  The basic framework for
    this capability has always been in place, and this change only provides the
    final implementation that actually generates and sends the e-mail message.
    
    This also includes a change to the way that log messages are handled so that
    any messages logged by a thread executing a task (or any DirectoryThread
    subclass created by a task thread) will be captured as part of that task.
    These messages will also be included in the notification e-mail message.
    
    OpenDS Issue Numbers:  2033, 2034
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2529 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • …re connections in both the status command-line and the status panel.  Some options to specify a keystore, a trustore, etc. have been added to the status command-line so that is consistent with the other command-lines that use LDAP.  As for these command-lines if the user does not specify to use Start TLS or LDAPS, the command-line will try to use LDAP to connect. But if there is no LDAP port enabled, the command-line will try to connect to the LDAPS port.
    
    Concerning the status panel, it will try to use the most secure method to connect to the server, if the servers is configured to use SSL or Start TLS and the presented certificate is not trusted by default by the JDK, we will present to the user in order to be accepted. 
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2521 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2520 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • …ngleton meant that multiple instances of dsconfig would share the same help sub-system and re-initialize it, potentially causing problems.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2519 41b1ffd8-f28e-4786-ab96-9950f0a78031
    matthew_swift
     
  • git-svn-id: https://svn.forgerock.org/opendj/trunk@2518 41b1ffd8-f28e-4786-ab96-9950f0a78031
    lutoff
     
  • …essage file in anticipation of forthcoming i18n improvements.
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2517 41b1ffd8-f28e-4786-ab96-9950f0a78031
    matthew_swift
     
  • git-svn-id: https://svn.forgerock.org/opendj/trunk@2516 41b1ffd8-f28e-4786-ab96-9950f0a78031
    lutoff
     
  • Force the processes launched by the installer and the upgrader to use the same JVM as the tools (th
    is is done by setting the JAVA_HOME environment variable when creating the processes).
    
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2515 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • be used to terminate client connections that have been idle for too long.  This
    can be controlled on a server-wide default level using the
    ds-cfg-idle-time-limit configuration attribute in the cn=config entry, but it
    can also be overridden on a per-user level with the ds-rlim-idle-time-limit
    operational attribute in the user's entry.
    
    Note that while the idle time limit support is server wide, it needs help from
    the connection handler to provide an idle time for client connections.  At this
    time, only the LDAP connection handler provides this capability.  It is not
    appropriate for internal connections, and it is not seen as important for JMX
    connections at this time (although such support could be added in the future if
    the need arises).
    
    OpenDS Issue Number:  118
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2514 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson