13 Sep, 2007
6 commits
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@3046 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@3044 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…nt with java.security.cert.CertificateException) git-svn-id: https://svn.forgerock.org/opendj/trunk@3038 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@3037 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@3036 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@3035 41b1ffd8-f28e-4786-ab96-9950f0a78031
12 Sep, 2007
6 commits
-
1335: define, document, review CLI to register a server in a synch 1336: CLI implementation to register a server in a synchronization 1878: provide a CLI to initialize a replication topology from a gi 2201: ads-trustore missing when not configuring replication with t 2250: Setup and dsreplication utilities should configure schema sy Extra: do not show dc=replicationchanges suffix in the replication panel of the setup, nor propose it to replicate. fix some bugs related to duplicate error messages displayed in dsreplication interactive mode. git-svn-id: https://svn.forgerock.org/opendj/trunk@3031 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@3030 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…sconfig would just bomb out. With this change dsconfig will either give the user the opportunity to re-edit and fix any mis-configured properties of the component (for create-xxx and set-xxx-prop interactive modes), or drop them back to the component menu (for delete-xxx interactive mode). dsconfig will still bomb out when it encounters a communication or security related problem. git-svn-id: https://svn.forgerock.org/opendj/trunk@3029 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…ere an applyConfigurationDelete was being invoked and throwing an IllegalStateException for changes that were not applicable to it. git-svn-id: https://svn.forgerock.org/opendj/trunk@3028 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@3025 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
- Update the server code to replace simple uses of ReentrantLock involving {lock, doSomething, unlock} in the same method to use the synchronized keyword instead of a ReentrantLock object. Using the synchronized keyword is actually a little faster, and also simplifies the code since it's no longer necessary to use a finally block to ensure that the lock is released. - Update the AsynchronousTextWriter to use the LinkedBlockingQueue.drainTo() method to attempt to get multiple messages at once, rather than always using poll() to get one message at a time. git-svn-id: https://svn.forgerock.org/opendj/trunk@3024 41b1ffd8-f28e-4786-ab96-9950f0a78031
11 Sep, 2007
9 commits
-
Previous to this change referential integrity was only enforced when a referencing (aggregating) component was added or modified. The support did not prevent a referenced component from being disabled or deleted. This change adds this remaining support: * a component cannot be deleted if it is referenced by one or more components * a component cannot be disabled if it is referenced by one or more components (it is possible to restrict this constraint so that it only applies when the referencing component(s) are enabled) This implementation only enforces referential integrity for referencing components which have listeners associated with them. For example, if component A references component B, then referential integrity will only be enforced automatically if component A has a change listener registered against it, or if it is "added" using an add listener that was registered against its parent. In effect, referential integrity is only enforced for components which are in use or are about to be used. git-svn-id: https://svn.forgerock.org/opendj/trunk@3023 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@3021 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…op background thread if needed. git-svn-id: https://svn.forgerock.org/opendj/trunk@3020 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@3018 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@3017 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@3013 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
may not be properly notified when the associated entry is updated. git-svn-id: https://svn.forgerock.org/opendj/trunk@3008 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
FIFO ordering. git-svn-id: https://svn.forgerock.org/opendj/trunk@3007 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
improvements, including: - Replace occurrences of StringBuffer with StringBuilder. As of Java 5, StringBuilder is almost always a better choice than StringBuffer because it provides all the same methods but doesn't have the synchronization overhead. - Update the JE backend DN2URI class (which is responsible for keeping track of smart referrals in the database) to keep track of whether there are any referrals in the underlying database so that it doesn't go to the DB if it can be certain that there aren't any referrals to get. - Update the JE backend ImportJob class to provide a simple cache for parent ID lookups so that it can avoid the need to go to the underlying DB to get the entry ID for a parent entry if it's contained in the cache. - Update the salted password storage scheme variants so that they use an instance of java.util.Random rather than java.security.SecureRandom to generate the salt. There really isn't a need for a cryptographic-quality random number generator for salt generation, and the java.util.Random implementation is much faster than the java.security.SecureRandom implementation. - Update the DN class to return a reference to the precomputed NULL_DN instead of creating a new DN with zero RDN components when decoding DNs from strings or octet strings. Also, use LinkedList rather than ArrayList for temporary storage of RDN values to avoid the hit of allocating memory that we may not need. - Update the Entry class to cache the result of LDIFImportConfig.typesOnly(), which has been observed to slightly improve MakeLDIF performance. - If Java 6 is available, then prefer using it to set file permissions over Runtime.exec() on UNIX systems. Even though it's potentially less fine-grained than using exec to call chmod, it's faster and safer to use the Java methods if they're available. git-svn-id: https://svn.forgerock.org/opendj/trunk@3006 41b1ffd8-f28e-4786-ab96-9950f0a78031
10 Sep, 2007
4 commits
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@3005 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
Set the proper port in the UserData object. Add some logging lines that might be helpful to fix other issues that we could have in this area of the code. git-svn-id: https://svn.forgerock.org/opendj/trunk@3004 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@3003 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
The AES, RC4, and Blowfish implementations all use 128-bit ciphers, and the 3DES implementation uses a 168-bit cipher. Note that while these password storage schemes are functional, they rely on the crypto manager, which is not fully implemented. The storage schemes are not exposed in the server configuration because the crypto manager does not have any mechanism to persist secret keys for symmetric encryption. Until the crypto manager provides persistence for these keys, passwords encoded using these schemes will not be usable after the server is restarted. Once the crypto manager implementation is complete, these schemes should be exposed in the server configuration. OpenDS Issue Numbers: 315, 316, 317, 318 git-svn-id: https://svn.forgerock.org/opendj/trunk@3000 41b1ffd8-f28e-4786-ab96-9950f0a78031
09 Sep, 2007
3 commits
-
will be invoked. There are two basic changes: - Add a new ds-cfg-invoke-for-internal-operations configuration attribute for all plugins, which indicates whether the plugin should be invoked for internal operations. If this is false, then the plugin will only be invoked for externally-requested operations. - Add four new plugin types: postSynchronizationAdd, postSynchronizationDelete, postSynchronizationModify, and postSynchronizationModifyDN. These allow a plugin to perform a limited set of processing for changes that are successfully applied through synchronization. The unique attribute plugin has also been updated to support the post-synchronization plugin types so that if a conflict is introduced concurrently on two different servers within the propagation delay, an administrative alert will be generated to indicate that manual intervention is required to address the problem. Finally, ensure that audit logging is enabled during the unit tests, and update the audit logger to include the connection ID and operation ID for the operation being logged. OpenDS Issue Number: 2057 git-svn-id: https://svn.forgerock.org/opendj/trunk@2999 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
implement generic entry cache monitor provider which allows any entry cache implementation current or future to provide a common or custom set of entry cache state data. update all existing entry cache implementations so that they provide their common state data to the entry cache monitor provider. git-svn-id: https://svn.forgerock.org/opendj/trunk@2998 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
CryptoManager Refactor to separate key and key entry generation from key retrieval. git-svn-id: https://svn.forgerock.org/opendj/trunk@2997 41b1ffd8-f28e-4786-ab96-9950f0a78031
08 Sep, 2007
1 commit
-
CryptoManager encryption Allow key size different from block size for block ciphers that support it (e.g., Blowfish as in Blowfish/CFB/NoPadding", 128) and block ciphers modes that use no initialization vector (e.g., ECB as in "DES/ECB/PKCS5Padding", 64). Note that this is accomplished without adding an initialization vector parameter to the encryption API. Instead, if the Cipher.getBlockSize is non-zero, the Cipher object is first instantiated with that size initialization vector, and if that fails, initialized without an initialization vector. git-svn-id: https://svn.forgerock.org/opendj/trunk@2996 41b1ffd8-f28e-4786-ab96-9950f0a78031
07 Sep, 2007
6 commits
-
…t does not exist. It will be needed by a stand-alone server instance to encrypt secret keys. git-svn-id: https://svn.forgerock.org/opendj/trunk@2994 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2993 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…guration entry instead of hard-wiring it. git-svn-id: https://svn.forgerock.org/opendj/trunk@2992 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
5 commits
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2983 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2979 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