08 Nov, 2007
3 commits
-
cate since this can break some clients. git-svn-id: https://svn.forgerock.org/opendj/trunk@3425 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
Fix the copy/paste errors in the description of the destination server arguments for the dsreplication initialize sub-command. git-svn-id: https://svn.forgerock.org/opendj/trunk@3424 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…up and status command-lines in the formatting and in the format used to present certificates to the user. Fix some bugs in the way the ADS was updated when an instance is uninstalled. git-svn-id: https://svn.forgerock.org/opendj/trunk@3423 41b1ffd8-f28e-4786-ab96-9950f0a78031
07 Nov, 2007
6 commits
-
…ent the local host fully qualified name. git-svn-id: https://svn.forgerock.org/opendj/trunk@3422 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…one because self-signed certificates are used for test and evaluation. During test and evaluation installing several instances in the same host is quite common, so having a different subject DN per instance is helpful to help identifying the instance. Moreover since the code of the tools uses the subject DN of the certificate as alias we can use the same keystore for all the servers installed on the same machine that use a self-signed certificate. git-svn-id: https://svn.forgerock.org/opendj/trunk@3421 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@3420 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…he case where an instance was uninstalled (but the registry not properly cleaned up) and we want to register it again. Instead of failing with an 'already registered' error, the code will try to update the registration information in the ADS. git-svn-id: https://svn.forgerock.org/opendj/trunk@3419 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@3418 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…he connections correspond to the source and which to the destination of the initialization. git-svn-id: https://svn.forgerock.org/opendj/trunk@3417 41b1ffd8-f28e-4786-ab96-9950f0a78031
06 Nov, 2007
3 commits
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@3416 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
The attributes : ds-cfg-max-receive-queue, ds-cfg-max-receive-delay, ds-cfg-max-send-queue, ds-cfg-max-send-delay were left from some prototyping I did a while ago and not usefull for now. I've therefore removed them from the configuration of the Replication Domain. git-svn-id: https://svn.forgerock.org/opendj/trunk@3415 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
extended operation handler. OpenDS Issue Number: 2563 git-svn-id: https://svn.forgerock.org/opendj/trunk@3414 41b1ffd8-f28e-4786-ab96-9950f0a78031
05 Nov, 2007
9 commits
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@3413 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@3412 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
The setup will automatically initialize the schema of the local server with the schema of the remote server. A new argument has been added to dsreplication enable (useSecondServerAsSchemaSource) to allow the user to specify which server must be used to initialize the schema of the other. The usage of this argument is: Use the second server to initialize the schema of the first server. If this option nor option {noSchemaReplication} are specified the schema of the first server will be used to initialize the schema of the second server git-svn-id: https://svn.forgerock.org/opendj/trunk@3411 41b1ffd8-f28e-4786-ab96-9950f0a78031 -
class that was generating a javadoc error. git-svn-id: https://svn.forgerock.org/opendj/trunk@3410 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@3409 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…d. The code of the command-line CLI has been updated to propose free ports. Fix a problem with an extra line that was added. git-svn-id: https://svn.forgerock.org/opendj/trunk@3408 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…he new options now ask for the different questions using the MenuBuilder methods and the methods defined in the ConsoleApplication class. git-svn-id: https://svn.forgerock.org/opendj/trunk@3407 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@3406 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
This code implements the importLDIF methods of the schema backend so that the replication total update is now usable on cn=schema git-svn-id: https://svn.forgerock.org/opendj/trunk@3405 41b1ffd8-f28e-4786-ab96-9950f0a78031
02 Nov, 2007
7 commits
-
OpenDS Issue Number: 2559 git-svn-id: https://svn.forgerock.org/opendj/trunk@3404 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
allow an entry to be modified if it was associated with an invalid or nonexistent password policy. This even prevented administrators from re-associating the entry with a valid password policy. With this change, the server will fall back to the default password policy for modify operations if the user-specific policy cannot be retrieved. OpenDS Issue Number: 2492 git-svn-id: https://svn.forgerock.org/opendj/trunk@3403 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
- Replace a couple of errant uses of SUBSTRINGS with SUBSTR. - Replace an errant "TOP" with "SUP top" in an object class definition. - Insert a missing space between the last attribute name and the closing parenthesis in the MAY list of an object class definition. git-svn-id: https://svn.forgerock.org/opendj/trunk@3402 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
memory available when running the compileadmin target. git-svn-id: https://svn.forgerock.org/opendj/trunk@3401 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…tor to fail after 2 consecutive period with no heartbeat detected git-svn-id: https://svn.forgerock.org/opendj/trunk@3400 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…ing different cases of entry sizes and buffer sizes git-svn-id: https://svn.forgerock.org/opendj/trunk@3399 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
… and dsconfig command lines by sharing the same code. The formatting of the table in status command-line has also be modified to be consistent with the one provided by dsconfig. git-svn-id: https://svn.forgerock.org/opendj/trunk@3398 41b1ffd8-f28e-4786-ab96-9950f0a78031
01 Nov, 2007
2 commits
-
Property name: org.opends.server.etime.nano Accepted values: true | false Default: false Fix for issue 2499 git-svn-id: https://svn.forgerock.org/opendj/trunk@3397 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@3396 41b1ffd8-f28e-4786-ab96-9950f0a78031
31 Oct, 2007
4 commits
-
… attributes with options and subtypes correctly when they are being indexed. With this fix: - All values of an indexed attribute type will be indexed correctly on modifies, adds, and deletes. - Updates to subordinate types will now update the superior type if its indexed. - Adding and deleting superior attribute types that are not allowed by any object classes (ie. name) will be correctly handled - Deleting all values from an attribute with no options will no longer delete the values from the same attribute but with options. git-svn-id: https://svn.forgerock.org/opendj/trunk@3395 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@3394 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@3393 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@3392 41b1ffd8-f28e-4786-ab96-9950f0a78031
30 Oct, 2007
6 commits
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@3391 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@3390 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@3389 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
Until now, the workflows were automatically configured-a wokflow was created for each base DN in the backends. When new suffixes were added or when a backend was added, the associated workflows were also created (and simillarly workflows were deleted as suffixes or backends were removed). With the manual mode, each and every workflow in the server must be defined explicitely in the configuration. By default, the server is running in automatic configuration mode. To have a server running with manual configuration mode one must set the attribute in cn=config: dn: cn=config ... ds-cfg-workflow-configuration-mode: auto|manual No attribute means "auto" mode. The workflow configuration consist of 3 parts: - the configuration of workfow elements - the configuration of workfows - the configuration of network groups The Workflow Elements - A workflow element is a basic task in a workflow. The workflow elements are organized in trees and the simplest tree is made of one element. For example, the workflow element that wraps a local backend is configured as follow: dn: ds-cfg-workflow-element-id=userRoot,cn=workflow elements,cn=config objectClass: top objectClass: ds-cfg-workflow-element objectClass: ds-cfg-local-backend-workflow-element ds-cfg-workflow-element-id: userRoot ds-cfg-enabled: true ds-cfg-java-class: org.opends.server.workflowelement.localbackend.LocalBackendWorkflowElement ds-cfg-backend: ds-cfg-backend-id=userRoot,cn=Backends,cn=config From an admin standpoint, the local backend workflow element is an aggregation of a single backend (attribute ds-cfg-backend). So we cannot disable/delete a backend as long as it is used by a local backend workflow element. The Workflows - A workflow is a chain of processing and it's targeting all the entries under a given baseDN. The processing is actually identified by the root node of the task tree described above. The configuration of a workflow looks like: dn: ds-cfg-workflow-id=userRoot,cn=workflows,cn=config objectClass: top objectClass: ds-cfg-workflow ds-cfg-workflow-id: userRoot ds-cfg-enabled: true ds-cfg-workflow-element: ds-cfg-workflow-element-id=userRoot,cn=workflow elements,cn=config ds-cfg-base-dn: dc=example,dc=com From an admin standpoint, the local workflow is an aggregation of a single elements (attribute ds-cfg-workflow-element). So we cannot disable/delete a workflow element as long as it is used by a local workflow. The Network Groups - A network group defines categories for client connection. The network group contains a set of workflows and each client operation is routed to one (or more) workflow(s). By default, the server create a default network group which contains all the workflows defined in the server. The default network group looks like: dn: ds-cfg-id=defaultNetworkGroup2,cn=network groups,cn=config objectClass: top objectClass: ds-cfg-network-group ds-cfg-id: defaultNetworkGroup2 ds-cfg-enabled: true ds-cfg-workflow: ds-cfg-workflow-id=adminRoot,cn=Workflows,cn=config ds-cfg-workflow: ds-cfg-workflow-id=ads-truststore,cn=Workflows,cn=config ds-cfg-workflow: ds-cfg-workflow-id=backup,cn=Workflows,cn=config ds-cfg-workflow: ds-cfg-workflow-id=config,cn=Workflows,cn=config ds-cfg-workflow: ds-cfg-workflow-id=monitor,cn=Workflows,cn=config ds-cfg-workflow: ds-cfg-workflow-id=schema,cn=Workflows,cn=config ds-cfg-workflow: ds-cfg-workflow-id=tasks,cn=Workflows,cn=config ds-cfg-workflow: ds-cfg-workflow-id=userRoot,cn=Workflows,cn=config From an admin standpoint, the network group is an aggregation of several workflows (attribute ds-cfg-workflow). So we cannot disable/delete a workflow as long as it is used by a network group. A unit test named WorkflowConfigurationTest tests the configuration of network groups, workflows and workflow elements. git-svn-id: https://svn.forgerock.org/opendj/trunk@3388 41b1ffd8-f28e-4786-ab96-9950f0a78031 -
git-svn-id: https://svn.forgerock.org/opendj/trunk@3387 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@3386 41b1ffd8-f28e-4786-ab96-9950f0a78031