09 Mar, 2007
4 commits
-
case-insensitive manner. OpenDS Issue Number: 1348 git-svn-id: https://svn.forgerock.org/opendj/trunk@1364 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
see the usage information. Also, allow short identifiers to be requested using a forward slash in addition to a single dash (e.g., "/?" will be treated the same as "-?"). OpenDS Issue Number: 1345 git-svn-id: https://svn.forgerock.org/opendj/trunk@1362 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@1352 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…handler were doing some additional validation using the DN of the entry containing the ACI. These checks cannot be done by the ACI attribute syntax since it does not have the entry DN. Keep the ACI attribute syntax but put the syntax checks back into the ACI handler. git-svn-id: https://svn.forgerock.org/opendj/trunk@1351 41b1ffd8-f28e-4786-ab96-9950f0a78031
08 Mar, 2007
8 commits
-
Define a new attribute syntax for the aci attribute. Invalid values are now rejected by the core server before getting to the access control evaluation. git-svn-id: https://svn.forgerock.org/opendj/trunk@1350 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
to be included or excluded git-svn-id: https://svn.forgerock.org/opendj/trunk@1349 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
instance of an element and adding a different instance of the same element in the same modification that also depends on a third schema element which was added between the two. For example, if you tried to have a single modify operation that deleted an existing object class, added a new attribute type, and added a new object class that depended on the new attribute type, the operation would fail because when processing the removal of the object class the server would attempt to determine whether it was going to be re-added later in the operation and therefore attempted to decode any object class additions later in the operation. An error occurred when trying to decode the new object class because it depended on an attribute type that was not yet defined and the decode operation wasn't told to ignore unknown schema elements. OpenDS Issue Number: 1318 git-svn-id: https://svn.forgerock.org/opendj/trunk@1346 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…private constructor to the field declaration, and where appropriate, qualifies the field with "final". The motivations are: 1. Easier to find default field values (e.g., use an IDE's "go to declaration" mechanism). 2. Mark any field with "final" that does not have a reasonable default value (i.e., those that depend on some constructor argument) to help ensure the object is properly initialized. git-svn-id: https://svn.forgerock.org/opendj/trunk@1344 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
instead of four-digit years. Also, update other parts of the server that made reference to UTC times when they really meant "YYYYMMDDhhmmssZ" to the term "GMT" instead of "UTC" so there is no confusion about whether the year would be expressed in four digits or two. OpenDS Issue Number: 637 git-svn-id: https://svn.forgerock.org/opendj/trunk@1343 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
with different types of key stores, including generating self-signed certificates and certificate signing requests. OpenDS Issue Number: 410 git-svn-id: https://svn.forgerock.org/opendj/trunk@1342 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
to add an entry that already exist. Also suppress a spurious println forgotten in a previous commit. git-svn-id: https://svn.forgerock.org/opendj/trunk@1335 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
Add the capability to deal with schema changes made be editing the schema files : The core server provides a notification to the synchronization. The synchronization generates a pseudo changes and propagate it to the other LDAP servers through the synchronization servers. The core server is not yet able to provide the notification but this is the code for the synchronization part of the job with its associated unit test. git-svn-id: https://svn.forgerock.org/opendj/trunk@1334 41b1ffd8-f28e-4786-ab96-9950f0a78031
07 Mar, 2007
5 commits
-
- This commit does not allow for configuring the debug logger over protocol. It can only be configured on server startup using properties. - The settings specified during startup will remain in effect for the duration of the server. - All messages are printed to standard out. - Weaving could be turned off with the -DDEBUG_BUILD=false property when building the server. - By default, the debug logger is off on server startup. It could be enabled by using the -Dorg.opends.server.debug.enabled=true. - Debug targets may be defined with the -Dorg.opends.server.debug.target property. The syntax of this property can be found on the opends.dev.java.net documentation section. - Debug logging is turned on by default on unit tests and printed on test failure. - Default debug target for unit tests could be changed by using the -Dorg.opends.test.debug.target property. Fix for issue 836 git-svn-id: https://svn.forgerock.org/opendj/trunk@1333 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@1327 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
whitespace EOL. git-svn-id: https://svn.forgerock.org/opendj/trunk@1326 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
expression patterns to make them more readable by defining constants. The other changes included are: - support the "targattrfilters" target keyword - make the "search" right behave correctly - fix a bug in the way we evaluate multiple permission bind rule pairs - the targetattr wild-card "*" will now not return operational attributes; operational attributes now need to be explicitly defined in the targetattr rule to grant access git-svn-id: https://svn.forgerock.org/opendj/trunk@1325 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
The synchronization code now takes the attribute usage into account so that values associated with an attribute type with a usage of "dSAOperation" are not synchronized between instances git-svn-id: https://svn.forgerock.org/opendj/trunk@1323 41b1ffd8-f28e-4786-ab96-9950f0a78031
06 Mar, 2007
1 commit
-
…checks are made for increment as would be made for a replace. However, the access control handler needs to have the modified entry available so the access control handler is called later in the modify operation after the modified entry has been set. This change has been discussed with Mike and Neil. git-svn-id: https://svn.forgerock.org/opendj/trunk@1322 41b1ffd8-f28e-4786-ab96-9950f0a78031
02 Mar, 2007
4 commits
-
programmatically from within the same JVM as the server. This will make it much easier to call them from unit tests. OpenDS Issue Number: 1311 git-svn-id: https://svn.forgerock.org/opendj/trunk@1309 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
This was caused by a null pointer exception that we previously got away with but became noticable since the ACI cache update is now atomic. git-svn-id: https://svn.forgerock.org/opendj/trunk@1306 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…ion and using configure script. In the QuickSetup I added some code to *temporarily* select a port that is not being used for JMX. Today we do not inform the user of the existence of this port so this approach does not make things much worse and reduces the changes of port conflicts in general. Even in the case where we are not installing multiple instances of OpenDS the port 1689 might be in use by another process. git-svn-id: https://svn.forgerock.org/opendj/trunk@1303 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
The synchronization protocol already have some re-synchronization capabilities that allows the synchronization server to detect where to start from the changelog when a new LDAP server opens a session. These changes implements the ability to do this when a restore or an import is done when the LDAP server is online and already connected to a synchronization server. To achieve this the synchronization code, on notification from the core server that a restore or an import is starting, close the session to the synchronization server and restart it when the restore or import is finished. The synchronization protocol then does its job of negociating where to start from the changelog and resynchronizing the LDAP Server. The core server does not yet provide the notification to the changelog server but here if the synchronization part of the code along with some test for it. git-svn-id: https://svn.forgerock.org/opendj/trunk@1296 41b1ffd8-f28e-4786-ab96-9950f0a78031
01 Mar, 2007
8 commits
-
…ger.debugCought should be debugCaught). git-svn-id: https://svn.forgerock.org/opendj/trunk@1293 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…g when reading the ACI cache. Remove the linked list field from the Aci class and use the standard LinkedList instead. git-svn-id: https://svn.forgerock.org/opendj/trunk@1292 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
… from the new debug logging framework. Also removed some redundent exception printing calls in favor or just one debugCought. Replaced System.out.println calls in RootContainer and JebFormat to debugInfo calls. Fix for issue 854 git-svn-id: https://svn.forgerock.org/opendj/trunk@1291 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
debugEnter and debugConstructor calls. git-svn-id: https://svn.forgerock.org/opendj/trunk@1286 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@1285 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@1284 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
This removes old debug logging framework method calls that are going to be automatically instrumented by AspectJ. Non instrumented debug method calls are updated to use the new debug framework methods. However, the new debug logging framework is not yet active as the Aspects are not weaved in. After this revision, debug logging will be disabled in the server until the new AOP framework is complete. - Removed debugEnter and debugConstructor from all source files. - Removed CLASS_NAME static string for debug purposes. - Removed old debug logging framework. - Added new debug logging frameworking using AOP. - Added AspectJ binary and libraries. - Change all modified files copyrights to include 2007. git-svn-id: https://svn.forgerock.org/opendj/trunk@1282 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…atically instrumented by AspectJ. Non instrumented debug method calls are updated to use the new debug framework methods. However, the new debug logging framework is not yet active as the Aspects are not weaved in. After this revision, debug logging will be disabled in the server until the new AOP framework is complete. - Removed debugEnter and debugConstructor from all source files. - Removed CLASS_NAME static string for debug purposes. - Removed old debug logging framework. - Added new debug logging frameworking using AOP. - Added AspectJ binary and libraries. - Change all modified files copyrights to include 2007. git-svn-id: https://svn.forgerock.org/opendj/trunk@1280 41b1ffd8-f28e-4786-ab96-9950f0a78031
28 Feb, 2007
7 commits
-
should be presented based on its alias (aka its nickname). This is used both by server-side code which needs to present a certificate to clients, as well as by client-side code which needs to present a certificate to the server. OpenDS Issue Number: 1292 git-svn-id: https://svn.forgerock.org/opendj/trunk@1279 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
PasswordPolicy.requireSecureAuthentication (via PasswordPolicyState.getPolicy). I had missed this call in an earlier commit. git-svn-id: https://svn.forgerock.org/opendj/trunk@1277 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
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
27 Feb, 2007
1 commit
-
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
26 Feb, 2007
2 commits
-
… 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