13 Nov, 2007
1 commit
-
Make the setup command line to support properties files. Make the uninstall command line to support properties files. Support properties files in dsreplication for all the subcommand arguments. git-svn-id: https://svn.forgerock.org/opendj/trunk@3447 41b1ffd8-f28e-4786-ab96-9950f0a78031
12 Nov, 2007
1 commit
-
…of menus and in the order that questions to connect to the servers. Update the upgrade to use the same menus as the other command-lines. Do some minor changes in the uninstall command-line in order to be more consistent with dsconfig in the order where the connection parameters are provided. Fix a bug in ApplicationTrustManager related to the accepted certificates when there is a mismatch between the certificate and the host name. Do some refactorization of the code and remove the CliApplicationHelper class so that we use ConsoleApplication everywhere. git-svn-id: https://svn.forgerock.org/opendj/trunk@3435 41b1ffd8-f28e-4786-ab96-9950f0a78031
09 Nov, 2007
2 commits
-
1. The db directory is now automatically created if it doesn't alreadly exist. When changing the db directory, a message is now displayed to let the user know the files will have to be manually moved and the backend restarted. (Issue 1979) 2. The backend no longer uses the Database.count method in JE as it is too expensive for large databases. The count can also be inaccurate when concurrent operations are executing on the server. This was causing the getEntryCount method up to 20 seconds to return. The count is now obtained from the id2subtree index. If the count is not maintained or the index is corrupt, it will fall back to using Database.count. (Issue 2581 and Issue 2420) git-svn-id: https://svn.forgerock.org/opendj/trunk@3434 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…me in the dsreplication usage. git-svn-id: https://svn.forgerock.org/opendj/trunk@3428 41b1ffd8-f28e-4786-ab96-9950f0a78031
08 Nov, 2007
3 commits
-
The problem is that there is a timeout when reading the monitoring informations on the server and the code did not handle this properly. I have made the method Utils.getMessage to handle properly the case when a Topol ogyCacheException has not a Throwable cause. In addition to that the method ret urns a specific message when a timeout occurs. Finally the timeout thresold has been risen from 10 to 30 seconds to be able to read the topology. git-svn-id: https://svn.forgerock.org/opendj/trunk@3426 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
05 Nov, 2007
4 commits
-
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 -
git-svn-id: https://svn.forgerock.org/opendj/trunk@3409 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
-
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
1 commit
-
… 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
30 Oct, 2007
1 commit
-
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
29 Oct, 2007
1 commit
-
…o, added implementations of missing methods and fixed null pointer exception when doing export-ldif without running as a task. Issue 2350. git-svn-id: https://svn.forgerock.org/opendj/trunk@3384 41b1ffd8-f28e-4786-ab96-9950f0a78031
26 Oct, 2007
1 commit
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@3374 41b1ffd8-f28e-4786-ab96-9950f0a78031
24 Oct, 2007
1 commit
-
- fix ConcurrentModificationException in the Initialize task by using methods that lock the entry - fix unroutable message, by forwarding message only to the replication servers that have replica connected Miscellaneous improvements in error or debug traces git-svn-id: https://svn.forgerock.org/opendj/trunk@3364 41b1ffd8-f28e-4786-ab96-9950f0a78031
23 Oct, 2007
2 commits
-
The following changes are aimed to include a new attribute in the backend monitor entry to provide the number or entries per base DN. This information is used by the status, status-panel, dsreplication and graphical setup to be able to display the number of entries under a given base DN even when there are several base DNs defined in the same database. The way the new attribute appears in the monitoring entry is: ldapsearch -w s -p 1389 -b cn=monitor ds-backend-id=userRoot ds-base-dn-entry-countdn: cn=userRoot Backend,cn=monitor ds-base-dn-entry-count: 0 dc=ta ds-base-dn-entry-count: 1 dc=ti ds-base-dn-entry-count: 1 dc=to I prefer this approach because in my opinion having the number of entries is more important that the suffix. Anyway I think the discussion around the structure of the value is not crucial as long as the value is easy to parse (which is the case). The new attribute is defined in the schema and the new OID assigned to it is 1.3.6.1.4.1.26027.1.1.434. In order to have a minimum impact on performances, the method backend.numSubordinates is only called when there are several base DNs defined in the database. git-svn-id: https://svn.forgerock.org/opendj/trunk@3361 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@3356 41b1ffd8-f28e-4786-ab96-9950f0a78031
22 Oct, 2007
3 commits
-
and 2496: setup : should not asking for key Store PIN in loop Update the code to avoid the NullPointerException and limit the number of times we ask for the Key Store PIN to 7. Once this limit is reached the setup is canceled. git-svn-id: https://svn.forgerock.org/opendj/trunk@3351 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
This changes the list formatting for property value lists so that each value is prefixed with a "*)" instead of a number and a bracket. This is done to avoid possible confusion with subsequent menu option numbers. git-svn-id: https://svn.forgerock.org/opendj/trunk@3348 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
This change modifies dsconfig so that it provides more helpful feedback to users when they need to provide string valued properties which must match a particular pattern. dsconfig now displays the pattern synopsis when requesting a property value or when reporting that a value is invalid. git-svn-id: https://svn.forgerock.org/opendj/trunk@3347 41b1ffd8-f28e-4786-ab96-9950f0a78031
19 Oct, 2007
1 commit
-
When the servers that are being replicated have a clock difference of more than 5 minutes inform the user of this. This is done in both the graphical setup and dsreplication tools. git-svn-id: https://svn.forgerock.org/opendj/trunk@3340 41b1ffd8-f28e-4786-ab96-9950f0a78031
18 Oct, 2007
1 commit
-
Add the rejectedFile and skippedFile options to the setup. git-svn-id: https://svn.forgerock.org/opendj/trunk@3336 41b1ffd8-f28e-4786-ab96-9950f0a78031
17 Oct, 2007
1 commit
-
CryptoManager RC4 -> RC4/NONE/NoPadding git-svn-id: https://svn.forgerock.org/opendj/trunk@3324 41b1ffd8-f28e-4786-ab96-9950f0a78031
16 Oct, 2007
3 commits
-
…if, export-ldif, backup, and restore) can now be interrupted for purposes of cancellation. The manage-tasks utility now allows the user to cancel any one of these tasks if they are currently running. If interrupted while executing, the tasks try to break out of their work loop as soon as possible and return a 'stopped by administrator' status. Both the backup and export-ldif tasks perform some cleanup (removing the abandoned backup or exported LDIF file) if they are cancelled. git-svn-id: https://svn.forgerock.org/opendj/trunk@3316 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@3311 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…eplica data , the replica must update the replication server with the missing changes. 1 line fix , the entryUUID attribute must be part of the searched attributes in order to rebuild the operations - and created unit tests for this. git-svn-id: https://svn.forgerock.org/opendj/trunk@3309 41b1ffd8-f28e-4786-ab96-9950f0a78031
15 Oct, 2007
1 commit
-
CryptoManager Add a single-byte version number prefix to the ciphertext prologue to allow for configurable options (e.g., signed hash in the backup stream). The current version produced and accepted is 0x01. git-svn-id: https://svn.forgerock.org/opendj/trunk@3308 41b1ffd8-f28e-4786-ab96-9950f0a78031
13 Oct, 2007
1 commit
-
CryptoManager - Add config test for encryption and key-wrapping cipher transformation syntax algorithm/mode/padding - elide duplicate configuration validation and assignment code git-svn-id: https://svn.forgerock.org/opendj/trunk@3302 41b1ffd8-f28e-4786-ab96-9950f0a78031
12 Oct, 2007
2 commits
-
…ns the ability to be rendered in locales different that the local locale. git-svn-id: https://svn.forgerock.org/opendj/trunk@3301 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@3299 41b1ffd8-f28e-4786-ab96-9950f0a78031
10 Oct, 2007
4 commits
-
bin/restore of encrypted or signed backup requires online server instance git-svn-id: https://svn.forgerock.org/opendj/trunk@3292 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
bin/backup --encrypt and --signHash require online backup git-svn-id: https://svn.forgerock.org/opendj/trunk@3289 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
remove redundant server property BACKUP_PROPERTY_CIPHER_ALGORITHM The cipher algorithm used is encoded in the backup data prologue. git-svn-id: https://svn.forgerock.org/opendj/trunk@3287 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
CryptoManger comment, todo cleanup git-svn-id: https://svn.forgerock.org/opendj/trunk@3284 41b1ffd8-f28e-4786-ab96-9950f0a78031
09 Oct, 2007
5 commits
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@3283 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
When importing a secret key entry from ADS into the crypto manager, if a symmetric key that can be decoded by this instance is not present then request it from another server using the Get Symmetric Key extended operation. Tested by configuring two servers to use 3DES password storage scheme in the default password policy, enabling replication between them and verifying that a user can bind with password to both instances. git-svn-id: https://svn.forgerock.org/opendj/trunk@3281 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
CryptoManager final i18n cleanup git-svn-id: https://svn.forgerock.org/opendj/trunk@3280 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
CryptoManager more i18n cleanup git-svn-id: https://svn.forgerock.org/opendj/trunk@3275 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
CryptoManager more i18n cleanup git-svn-id: https://svn.forgerock.org/opendj/trunk@3274 41b1ffd8-f28e-4786-ab96-9950f0a78031