03 Aug, 2007
4 commits
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2554 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2553 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2552 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2551 41b1ffd8-f28e-4786-ab96-9950f0a78031
02 Aug, 2007
6 commits
-
retrieve the task entry at the same time that it was being updated. git-svn-id: https://svn.forgerock.org/opendj/trunk@2550 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2549 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2548 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
Now --remove, --add, and --reset are options that can be used with set-xxx-yyy-prop command for dsconfig. --set is the default option. git-svn-id: https://svn.forgerock.org/opendj/trunk@2547 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2546 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2545 41b1ffd8-f28e-4786-ab96-9950f0a78031
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
-
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
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2541 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
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 -
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
31 Jul, 2007
9 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
-
…problems with the test machines git-svn-id: https://svn.forgerock.org/opendj/trunk@2537 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2536 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
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
-
…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
-
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 -
git-svn-id: https://svn.forgerock.org/opendj/trunk@2532 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
2. fixed bad function call for indexes_remove git-svn-id: https://svn.forgerock.org/opendj/trunk@2531 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…aking the functional tests. git-svn-id: https://svn.forgerock.org/opendj/trunk@2530 41b1ffd8-f28e-4786-ab96-9950f0a78031
30 Jul, 2007
16 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
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2528 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
… with dsconfig\n4.added entry limit test but disabled for now git-svn-id: https://svn.forgerock.org/opendj/trunk@2527 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2526 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2525 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2524 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2523 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…unction to change global ACIs in some functional tests. git-svn-id: https://svn.forgerock.org/opendj/trunk@2522 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…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
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2520 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…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
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2518 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…essage file in anticipation of forthcoming i18n improvements. git-svn-id: https://svn.forgerock.org/opendj/trunk@2517 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2516 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
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
-
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