14 Jun, 2007
4 commits
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2098 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
Re-enable JMX unit-tests (disabled in rev 2071 due to unit-test failure) git-svn-id: https://svn.forgerock.org/opendj/trunk@2097 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
build due to a number of missing symbols. git-svn-id: https://svn.forgerock.org/opendj/trunk@2095 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…sue 1779 for more info. git-svn-id: https://svn.forgerock.org/opendj/trunk@2094 41b1ffd8-f28e-4786-ab96-9950f0a78031
13 Jun, 2007
3 commits
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2092 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
I am commenting out this test case until I can find and restore the ldif file. git-svn-id: https://svn.forgerock.org/opendj/trunk@2091 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
I am commenting out this test case until I can find and restore the ldif file. git-svn-id: https://svn.forgerock.org/opendj/trunk@2090 41b1ffd8-f28e-4786-ab96-9950f0a78031
12 Jun, 2007
7 commits
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2085 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2083 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2081 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2080 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2079 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2078 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2077 41b1ffd8-f28e-4786-ab96-9950f0a78031
11 Jun, 2007
5 commits
-
…s which define a pattern constraint. The usage string is used when the syntax of a property needs to be displayed, for example in a CLI help screen or in server-side log messages when a bad property value is encountered. For example, a property whose values must be a valid UNIX mode could have the following string syntax definition: <adm:string> <adm:pattern> <adm:regex>^[0-7][0-7][0-7]$</adm:regex> <adm:usage>MODE</adm:usage> <adm:synopsis> An valid UNIX mode string. The mode string must contain three digits between zero and seven. </adm:synopsis> </adm:pattern> </adm:string> Existing string based properties have been updated with appropriate usage. git-svn-id: https://svn.forgerock.org/opendj/trunk@2073 41b1ffd8-f28e-4786-ab96-9950f0a78031 -
git-svn-id: https://svn.forgerock.org/opendj/trunk@2071 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2070 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
These changes are the last part of the naming conflict resolution. It also introduce the ds-sync-conflict attribute that is used to mark the entries for which an automatic conflict resolution is not possible. git-svn-id: https://svn.forgerock.org/opendj/trunk@2068 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2067 41b1ffd8-f28e-4786-ab96-9950f0a78031
08 Jun, 2007
1 commit
-
…the performance of the loggers when they are disabled. Fixed for issue 1780 git-svn-id: https://svn.forgerock.org/opendj/trunk@2059 41b1ffd8-f28e-4786-ab96-9950f0a78031
07 Jun, 2007
4 commits
-
use a privilege of "unindexed-search" instead. Also, eliminate the index-rebuild privilege and fold all of its functionality into ldif-import, since having a separate privilege for it doesn't provide much benefit and creates additional administrative overhead. OpenDS Issue Numbers: 1765, 1776 git-svn-id: https://svn.forgerock.org/opendj/trunk@2051 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
for entries in private backends (e.g., the root DSE, schema, monitor entries, config entries, etc.). The entryUUID value that will be generated is based on an MD5 hash of the entry DN, but this shouldn't be a problem for entries in private backends because none of them allow modify DN operations. User entries should have a real entryUUID value generated when the entry is created (either via an LDAP add or an LDIF import). OpenDS Isssue Number: 1775 git-svn-id: https://svn.forgerock.org/opendj/trunk@2050 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
element that includes flags that indicate how the entry was encoded. The flags currently defined include: - Whether to exclude the DN from the encoded entry. This may be useful for the filesystem entry cache, since it will already have a reference to the DN. - Whether to compress the set of object classes contained in the entry with a binary token. - Whether to compress the attribute descriptions in the entry with binary tokens. These changes can help improve the encode/decode performance, and can reduce the entry footprint (by about 30% for entries based on the example.template). None of these options are enabled at the present time, but components which call the Entry.encode() method will be able to indicate which of them should be used for that entry. OpenDS Issue Numbers: 660, 1675, 1770 git-svn-id: https://svn.forgerock.org/opendj/trunk@2049 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
Considering the limited added value that the JMX port will provide on 1.0 and the fact that we do not want to expose it on the QuickSetup, in the admin group we consider to disable this port by default. Before committing a fix for this maybe we should send a Heads Up message to the users mailing list. Basically after the changes the JMX connection handler will not be enabled if the server is installed using the graphical setup. For the command line setup, JMX will not be enabled unless the user explicitly includes de -x option (for the JMX port) when invoking the command-line. git-svn-id: https://svn.forgerock.org/opendj/trunk@2046 41b1ffd8-f28e-4786-ab96-9950f0a78031
06 Jun, 2007
3 commits
-
directory. In particular, this commit exposes the LDAPClientConnection.sendLDAPMessage() method, and fixes a case in which short-circuiting out of the add operation processing in the pre-parse code with a success response could have resulted in a null pointer exception. OpenDS Issue Number: 1729 git-svn-id: https://svn.forgerock.org/opendj/trunk@2045 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
ldapCompareWithScript, and ldapPasswordModifyWithScript. git-svn-id: https://svn.forgerock.org/opendj/trunk@2044 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2038 41b1ffd8-f28e-4786-ab96-9950f0a78031
05 Jun, 2007
2 commits
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2022 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2020 41b1ffd8-f28e-4786-ab96-9950f0a78031
04 Jun, 2007
4 commits
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2016 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…Issues 1600 and 1762. git-svn-id: https://svn.forgerock.org/opendj/trunk@2013 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2012 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
The resolution procedure for single valued attribute needs to be slightly different from the mult-valued attribute procedure : - less historical information can be kept - the procedure must take into account the fact that only one value is allowed at a given time. This Change splits the AttrInfo class into 2 classes : AttrInfoSingle and AttrInfoMultiple that both extends AttributeInfo. The Historical class if also refactorized to become more generic, some code was staying there but was indeed specific to multi-valued attribute. This change also add a number of unit tests for single valued attribute, and enable an old test from HistoricalTest.java that was previously disabled because conflict resolution for single valued attribute was not yet implemented. git-svn-id: https://svn.forgerock.org/opendj/trunk@2004 41b1ffd8-f28e-4786-ab96-9950f0a78031
02 Jun, 2007
1 commit
-
server will only allow client connections over loopback interfaces and will reject requests from non-root users. This can be used in cases where it would be helpful for the server to be online to address a problem, but there might be security risks in having it fully available (e.g., the server detects a malformed access control rule on startup, and we don't want to allow normal access to the server since that rule might be intended to prevent users from seeing sensitive information and not having it interpreted properly could be dangerous). This mode is designed so that server components like the access control subsystem can place the server in this mode if a problem is detected, but it also includes tasks that can be used to manually place the server into and out of the lockdown mode. These tasks will only be allowed to be invoked by root users over a loopback connection. OpenDS Issue Number: 1758 git-svn-id: https://svn.forgerock.org/opendj/trunk@2002 41b1ffd8-f28e-4786-ab96-9950f0a78031
01 Jun, 2007
6 commits
-
a function that creates a backup that's used in the restore1 testcase. git-svn-id: https://svn.forgerock.org/opendj/trunk@1999 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@1998 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
always based on the authentication identity rather than the authorization identity. This means that when the two are different, the result could be incorrect. One key example of this is the use of the proxied authorization control by a root user. In this case, the proxied authorization would not be subject to access control because the authenticated user (but not the authorized user) had the bypass-acl privilege. This change ensures that the proxied-auth privilege is always evaluated as the authentication identity, but all other priviliges are always evaluated as the authorization identity. I have also updated a number of test cases that were incorrectly depending on the former behavior. OpenDS Issue Number: 1749 git-svn-id: https://svn.forgerock.org/opendj/trunk@1997 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@1996 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
… more user-friendly encode/decode methods: * the DurationPropertyDefinition encoder is unchanged: it uses the base property's base unit * the DurationPropertyDefinition decoder now supports a mixed format in addition to the old format: now users can specify durations using a mixture of units such as 1h30m instead of 90m (both are permitted) * the DurationUnit class has a toString(long) method which applications can use to get the above mixed unit representation (e.g. CLI) The unit tests are updated. During the precommit the password policy test cases failed because they were testing some invalid durations which were not being checked in the DurationPropertyDefinition test suite. I've put these missing test cases in the DurationPropertyDefinition test suite. In addition, I've numbered the PWP test data entries so that they are easier to debug in future. git-svn-id: https://svn.forgerock.org/opendj/trunk@1995 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@1994 41b1ffd8-f28e-4786-ab96-9950f0a78031