28 Feb, 2007
7 commits
-
PasswordPolicy.requireSecureAuthentication (via PasswordPolicyState.getPolicy). I had missed this call in an earlier commit. git-svn-id: https://svn.forgerock.org/opendj/trunk@1276 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
configuring synchronization for suffix cn=schema (issue 613) . You may want to read the schema Synchronization documents before reviewing this https://opends.dev.java.net/public/docs/dev-docs/SchemaSyncFeatureRequirements.html and https://opends.dev.java.net/public/docs/dev-docs/SchemaSyncDesign.html It includes : - Change the PersistentServerState to use attribute ds-sync-state in the base entry instead of a specific entry. Add new unit test for the PersistentServerState class. Change attribute ds-sync-state to be an operational attribute. - Change the schema backend to allow storage of the ds-synch-state attribute in the schema ldif File. This change is arguable because I have chosen to make this as simple as possible and therefore only allowed the storage of this attribute in the schema File. While this has the advantage of being very simple it has the drawback of adding some code in the schema backend that is only related to synchronization. The other choice would be to add a generic service in the schema backend for storing any type of attribute. Please tell me if you think that this would be better. - Disable the conflict resolution for cn=schema so that we don't polute the ldif entries with the historical information - Add unit test for schema synchronization The work for schema synchronization is not complete with this. A second round of modification is necessary for synchronizing the schema changes done by manually editing the files or by dynamically loading a file. git-svn-id: https://svn.forgerock.org/opendj/trunk@1275 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
This change makes possible to configure the Changelog purge delay that was previously hard-coded using the ds-cfg-changelog-purge-delay attribute. git-svn-id: https://svn.forgerock.org/opendj/trunk@1274 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@1273 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
The problem was caused because in the class InstallDS the check for the port was not performed when the user already provided the port through the command line (see first diffs in InstallDS). The rest of the diffs consist of factorization of code to be shared between the quicksetup classes and the class org.opends.server.tools.InstallDS. Some methods from the Utils class of quicksetup have been moved to the SetupUtils class; these methods allow to know if a given port is priviledged or not, if we can use it to configure the server and to know in which Operating System the JVM is running. The operating system methods use the enumeration OperatingSystem (which has been slightly modified to not have dependencies on other classes and to be included in quicksetup.jar). Extra: use the class LockFileManager to know if the server is running or not. The use of this class does not impact the Web Start Installer as we only want to know if the server is running or not once we have tried to start it (and so OpenDS.jar has already been loaded by the class loader). git-svn-id: https://svn.forgerock.org/opendj/trunk@1272 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
draft-wahl-ldap-session and the new draft-zeilenga-sasl-yap document. git-svn-id: https://svn.forgerock.org/opendj/trunk@1270 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
. run the functional tests on windows . download the daily build and install it to run the functional tests . gather test coverage by editing the package on the fly to launch emma git-svn-id: https://svn.forgerock.org/opendj/trunk@1269 41b1ffd8-f28e-4786-ab96-9950f0a78031
27 Feb, 2007
4 commits
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@1267 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@1265 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
Neil for issue #1266: use a hidden option to check whether the server is already running or not. If the server is not running the message 'Server already stopped' is displayed, if the server is running the message 'Stopping Server... is displayed'. So the output of the command with this changes is: If the server is running ======================== bash-3.00$ bin/stop-ds --restart Stopping Server... [23/Feb/2007:17:00:28 +0100] category=CORE severity=NOTICE id=458886 msg="OpenDS Directory Server 0.1.0 starting up." [23/Feb/2007:17:00:34 +0100] category=BACKEND severity=NOTICE id=8847402 msg="A database backend containing 1 entries has started." [23/Feb/2007:17:00:34 +0100] category=CONFIG severity=SEVERE_WARNING id=3277325 msg="Access control has been disabled." [23/Feb/2007:17:00:35 +0100] category=CORE severity=NOTICE id=458887 msg="The Directory Server has started successfully." [23/Feb/2007:17:00:35 +0100] category=CORE severity=NOTICE id=458891 msg="The Directory Server has sent an alert notification generated by class org.opends.server.core.DirectoryServer (alert type org.opends.server.DirectoryServerStarted, alert ID 458887): The Directory Server has started successfully.." bash-3.00$ bash-3.00$ bin/stop-ds If the server is stopped ======================== bash-3.00$ bin/stop-ds Server already stopped. bash-3.00$ bin/stop-ds --restart Server already stopped. [23/Feb/2007:16:59:50 +0100] category=CORE severity=NOTICE id=458886 msg="OpenDS Directory Server 0.1.0 starting up." [23/Feb/2007:16:59:55 +0100] category=BACKEND severity=NOTICE id=8847402 msg="A database backend containing 1 entries has started." [23/Feb/2007:16:59:56 +0100] category=CONFIG severity=SEVERE_WARNING id=3277325 msg="Access control has been disabled." [23/Feb/2007:16:59:57 +0100] category=CORE severity=NOTICE id=458887 msg="The Directory Server has started successfully." [23/Feb/2007:16:59:57 +0100] category=CORE severity=NOTICE id=458891 msg="The Directory Server has sent an alert notification generated by class org.opends.server.core.DirectoryServer (alert type org.opends.server.DirectoryServerStarted, alert ID 458887): The Directory Server has started successfully.." git-svn-id: https://svn.forgerock.org/opendj/trunk@1263 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
the new certificate mappers, as well as the ds-cfg-changelog-purge-delay attribute. git-svn-id: https://svn.forgerock.org/opendj/trunk@1262 41b1ffd8-f28e-4786-ab96-9950f0a78031
26 Feb, 2007
11 commits
-
The start TLS test suite no longer allows the rest of the tests to run without failing. git-svn-id: https://svn.forgerock.org/opendj/trunk@1261 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@1260 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@1259 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@1258 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@1257 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@1256 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
… in the control panel in the class Utils.java. git-svn-id: https://svn.forgerock.org/opendj/trunk@1255 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
- One which will take attributes from the certificate subject and map them to attributes in user entries (Issue #1278). - One which will search for the subjects of the presented certificates in user entries (Issue #1279). - One which will search for the MD5 or SHA1 fingerprints of the presented certificates in user entries (Issue #1280). git-svn-id: https://svn.forgerock.org/opendj/trunk@1254 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@1253 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@1252 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@1251 41b1ffd8-f28e-4786-ab96-9950f0a78031
23 Feb, 2007
15 commits
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@1250 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
OpenDS Issue Number: 1277 git-svn-id: https://svn.forgerock.org/opendj/trunk@1249 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…s) did not check for null OperationStatus objects being passed in and caused an NullPointerException whenever EntryCount was called. Added a null check. Changed ID2Entry#getRecordCount to use the Database#count method in JE 3.1.0. The JE backend no longer keeps a count of entries in entry ID 0. Modified TestVerifyJob unit test to no longer simulate a incorrect entry count. It was a clear case that using Database#count is much faster then keeping a count at entryID 0. At the least, it can eliminate a database read and write on every entry add and delete operation. In addition, calling Database#count is faster then getting an entry out of the database as the following shows. Time took to get entry count 100 times (w/o transactions): Duration using Database#count: 16731000 ns Duration using old entry counter: 22094000 ns Duration using Database#count: 17124000 ns Duration using old entry counter: 39434000 ns Duration using Database#count: 15522000 ns Duration using old entry counter: 20069000 ns Duration using Database#count: 15873000 ns Duration using old entry counter: 19732000 ns Duration using Database#count: 15871000 ns Duration using old entry counter: 20594000 ns Duration using Database#count: 21099000 ns Duration using old entry counter: 21877000 ns Fix for issue 740 git-svn-id: https://svn.forgerock.org/opendj/trunk@1247 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…r enabled. The testDigestMD5 test in LDAPCompareTestCase was not actually binding using DigestMD5 because the SASL mechanism name was omitted from the arguments. git-svn-id: https://svn.forgerock.org/opendj/trunk@1246 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
introduced a large number of test failures. git-svn-id: https://svn.forgerock.org/opendj/trunk@1245 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
… default. Most of the failing tests are fixed by adding bypass-acl privilege to the entries of the users the failing tests bind as. This change also includes an important fix to the server for operations carrying the proxied auth control. The ACI check in the core operation is moved after the controls processing to ensure that the correct authorization user is picked up, and the ACI handler now gets the authorization user from the operation rather than the connection. git-svn-id: https://svn.forgerock.org/opendj/trunk@1244 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
least one value. This will prevent add requests from being able to add entries containing attributes with no values. OpenDS Issue Number: 1275 git-svn-id: https://svn.forgerock.org/opendj/trunk@1241 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
about whether a given SSL certificate should be trusted. This will be used for all of our client tools in the case when no trust store is available and the user has not requested the "--trustAll" option. OpenDS Issue Number: 1274 git-svn-id: https://svn.forgerock.org/opendj/trunk@1240 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@1239 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
we don't need in the core server but can help other applications interoperate with OpenDS. Also, add a class org.opends.server.interop.LazyDN which is a lazily-initialized version of the org.opends.server.types.DN class. This makes it possible to have very fast DN processing when you need to create a DN from a String and the only thing that will be called on that DN is the toString() method. This commit includes test cases to ensure that the public methods of the DN and LazyDN classes stay in sync. OpenDS Issue Number: 1276 git-svn-id: https://svn.forgerock.org/opendj/trunk@1238 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…e JE backend no longer keeps a count of entries in entry ID 0. Modified TestVerifyJob unit test to no longer simulate a incorrect entry count. Fix for issue 740 git-svn-id: https://svn.forgerock.org/opendj/trunk@1237 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
"%*" Does not work properly when we have arguments with quotes. Use a FOR statement to determine whether the user provided arguments or not to the stop-ds.bat command. git-svn-id: https://svn.forgerock.org/opendj/trunk@1233 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@1232 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
the project that are not appropriate for inclusion below trunk/opends or other official project locations. See trunk/scratch/README for more information and usage guidelines. OpenDS Issue Number: 1127 git-svn-id: https://svn.forgerock.org/opendj/trunk@1231 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
are intended only for internal use. git-svn-id: https://svn.forgerock.org/opendj/trunk@1230 41b1ffd8-f28e-4786-ab96-9950f0a78031
22 Feb, 2007
3 commits
-
notification whenever the access control handler is enabled or disabled. OpenDS Issue Number: 1269 git-svn-id: https://svn.forgerock.org/opendj/trunk@1229 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
the dseecompat implementation by default. It will still remain disabled by default. OpenDS Issue Number: 1270 git-svn-id: https://svn.forgerock.org/opendj/trunk@1228 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@1227 41b1ffd8-f28e-4786-ab96-9950f0a78031