07 Sep, 2007
9 commits
-
…guration entry instead of hard-wiring it. git-svn-id: https://svn.forgerock.org/opendj/trunk@2992 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2991 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2990 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2989 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2988 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2987 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
… backend API for the replication server changes database. In a first step, the implemented features are backup/restore. The coming ones will be export/search to have an LDAP access of the content of the replication server DB. I also cleaned/shared some code on replication unit tests. Also fixed a potential bug in the replication plugin on the total update by replacing any object dependency from the ReplicationDomain to the associated backend because the configuration changes on the backend object may replace this object by another instance, so keeping a reference on the backend instance is buggy. The instance must be retrieved when needed. git-svn-id: https://svn.forgerock.org/opendj/trunk@2986 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
… (e.g., "RC4"). Cipher.getBlockSize equal to 0 is used to detect this case, hence this implementation likely still does not support block cipher modes that do not accept initialization vectors (e.g., ECB). One additional remaining inadequacy is the case where the initialization vector is not the same length as the encryption key (e.g., ""Blowfish/CFB/NoPadding" allows a key length up to 448 bits, but the initialization vector is always 64 bits). git-svn-id: https://svn.forgerock.org/opendj/trunk@2985 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2984 41b1ffd8-f28e-4786-ab96-9950f0a78031
06 Sep, 2007
13 commits
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2983 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
to acquire a lock file. The server was functioning properly, but the message should not have been printed. OpenDS Issue Number: 2242 git-svn-id: https://svn.forgerock.org/opendj/trunk@2982 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
assertions about the number of times that various kinds of plugins were invoked. A number of test cases making assertions about the invocation counts were failing pretty frequently, and after analyzing the problem it is not something that can be easily addressed. The underlying causes include: - Processing on unbind operations continuing in a separate thread from a previous test case. Whenever the client sends an unbind request to the server, it immediately disconnects and moves on to the next test case. However, the server may continue to read and process that unbind operation (including invoking plugins on it) in a separate thread. - For modify DN operations, the referential integrity plugin was sometimes responsible for invoking operations in the background that could increase the invocation count. git-svn-id: https://svn.forgerock.org/opendj/trunk@2981 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2980 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2979 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2978 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2977 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2976 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
- dsconfig interactive secure connection enhancement git-svn-id: https://svn.forgerock.org/opendj/trunk@2975 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
rather than storage scheme names. This will allow better consistency in the configuration, since all other references between configuration objects are DN-based, and it will work better with the upcoming aggregation support. It also eliminates the need to know the storage scheme name, which is not obvious from looking at the configuration entry for the storage scheme, and can actually vary in some implementations depending on whether it's used with a user password or auth password syntax attribute. OpenDS Issue Number: 2155 git-svn-id: https://svn.forgerock.org/opendj/trunk@2974 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…CS5Padding") or just algorithm (e.g., "AES") supply only the algorithm name to the SecretKeySpec initialization. 2. ByteString, ASN1OctetString -> ByteArray, ByteArray for Map key type. git-svn-id: https://svn.forgerock.org/opendj/trunk@2973 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…e adds a constraint which prevents configuration of dangling references. A subsequent change will add a constraint which will prevent removal of referenced components. git-svn-id: https://svn.forgerock.org/opendj/trunk@2972 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…perty definition is constructed. git-svn-id: https://svn.forgerock.org/opendj/trunk@2971 41b1ffd8-f28e-4786-ab96-9950f0a78031
05 Sep, 2007
18 commits
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2970 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…o server-side constraint enforcement call-backs: isUsable and isDeleteAllowed. The first is invoked whenever a managed object is decoded (except in the case where it's about to be deleted). The second is invoked whenever a managed object is about to be deleted. With this change we will now detect constraint violations during server initialization, not just when config change/add/delete events occur. git-svn-id: https://svn.forgerock.org/opendj/trunk@2969 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2968 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
This change adds support for "aggregation" properties, which are properties which reference other managed objects (see issue 1449 for more details). Subsequent changes will add server-side and client-side referential integrity support, as well as migrating components over to using them (this will be post MS1.0). git-svn-id: https://svn.forgerock.org/opendj/trunk@2967 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
- Adds a thread to synchronize the server instance certificates from the admin data branch to the local trust store backend. - Replaces the blind trust managers in the replication session with trust managers that use the local trust store. Note that replication must be configured using either setup-gui or the dsreplication command. git-svn-id: https://svn.forgerock.org/opendj/trunk@2966 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…ather than roomnumber and telephonenumber some of the functional tests. git-svn-id: https://svn.forgerock.org/opendj/trunk@2965 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
1. Encapsulate Cipher object in CryptoManager instance. 2. Cipher key identifier (tag) and initialization vector prefix the cipher text. 3. New API consists of encrypt and getOutputCipherStream (with optional cipher transformation parameter), and decrypt and getInputCipherStream. Limitations: This is an update of the API only. The keys are stored in a Map object in the CryptoManager instance, so 1. The implementation works for a single instance only (e.g., no encrypted passwords in a replication domain). 2. The key map does not persists across instance restarts. Both persistent key storage in a stand-alone instance and the secret key distribution protocol (via ADS) for replicated topologies needs to be implemented. Other shortcomings: 1. The exception messages need to be added to the message catalogue. 2. The implementation could benefit from a review. 3. Only simple success test cases are implemented in the unit tests. 4. The uses of getInputCipherStream and getOutputCipherStream should be reviewed, since the cipher transformation used - as of now it is always the preferred (default) cipher transformation - is still stored in the backup info file, where it might be informative, but is redundant (the cipher info is encoded as the prologue of the backup data). 5. The preferred cipher, etc., should be configurable. git-svn-id: https://svn.forgerock.org/opendj/trunk@2964 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2963 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
Use the --checkstartability option to know if the server is running or not and return the proper error code accordingly. git-svn-id: https://svn.forgerock.org/opendj/trunk@2962 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…performed from just -h (host) to also include -p (port) and -D (bind DN) git-svn-id: https://svn.forgerock.org/opendj/trunk@2961 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
- fix a buf (we don't need bindDN if client side authentication is required) git-svn-id: https://svn.forgerock.org/opendj/trunk@2960 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2959 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2958 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2957 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2956 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
follows: - Pending tasks and completed tasks may be deleted. Running tasks may not be deleted. - Any attributes in pending tasks may be modified. - Only the task state in running tasks may be modified, and only to cancel the task. - No attributes of a completed task may be modified. OpenDS Issue Number: 2181 git-svn-id: https://svn.forgerock.org/opendj/trunk@2955 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
… the setup command line: * 1257 setup cli/gui symetry -- allow to start after slient install * 1264 silent install option is not silent * 1326 Update setup CLI to integrate common install scenario (partial fix) * 1404 different CLI/GUI behavior running setup * 1859 spin off GUI specific CLI commands * 2184 setup quite/no-prompt * 2185 setup --cli -Q throws error The changes basically consist on splitting the current setup command-line into two (the same way we have done for the uninstall). Know we will have one command to launch the setup in CLI mode (setup and setup.bat) and one command to launch the setup in GUI mode (setup-gui and setup-gui.bat). The behavior of the graphical interface has not changed. However the capabilities of the CLI setup have been extended to allow to match those in the graphical interface (excluding the replication configuration capabilities): * Configure the LDAPS and StartTLS on the server. * Start the server. git-svn-id: https://svn.forgerock.org/opendj/trunk@2954 41b1ffd8-f28e-4786-ab96-9950f0a78031 -
…provded the messages when we prompt for the type of connection that the user wants to use to update configuration. Fixed a localization bug in SubCommandArgumentParser. git-svn-id: https://svn.forgerock.org/opendj/trunk@2953 41b1ffd8-f28e-4786-ab96-9950f0a78031