Return-Path: Delivered-To: apmail-directory-users-archive@www.apache.org Received: (qmail 75104 invoked from network); 15 May 2007 20:16:57 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 15 May 2007 20:16:57 -0000 Received: (qmail 24392 invoked by uid 500); 15 May 2007 20:17:04 -0000 Delivered-To: apmail-directory-users-archive@directory.apache.org Received: (qmail 24373 invoked by uid 500); 15 May 2007 20:17:03 -0000 Mailing-List: contact users-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@directory.apache.org Delivered-To: mailing list users@directory.apache.org Received: (qmail 24293 invoked by uid 99); 15 May 2007 20:17:03 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 May 2007 13:17:03 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (herse.apache.org: local policy) Received: from [81.169.146.162] (HELO mo-p00-ob.rzone.de) (81.169.146.162) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 May 2007 13:16:56 -0700 Received: from [127.0.0.1] ([213.83.33.75]) by post.webmailer.de (klopstock mo40) (RZmta 6.3) with ESMTP id A00094j4FIpCzW for ; Tue, 15 May 2007 22:16:32 +0200 (MEST) Message-ID: <464A1522.7020300@labeo.de> Date: Tue, 15 May 2007 22:16:34 +0200 From: Stefan Zoerner User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) MIME-Version: 1.0 To: users@directory.apache.org Subject: Re: adding a group without members on create References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-RZG-AUTH: kR2YrGeU3i5GJZNxbYfAbITnBeX/YWiFZ/RSZNkRrNDlTVxn1qCa4m8= X-RZG-CLASS-ID: mo00 X-Virus-Checked: Checked by ClamAV on apache.org Alex Karasulu wrote: > Although reported as a ApacheDS specific issue this may just be due to > lack of information about the behavior of other LDAP servers. I'm sure > other LDAP servers behave in the same manner when schema checking > is enabled. Hence I think it is incorrect to presume this is ADS specific. > > Alex You are totally right Alex. Two examples: IBM Tivoli Directory Server behaves like ApacheDS (uniqueMember is a MUST attribute in groupOfUniqueNames, as stated in the RFC), Sun Java System Directory Server does not (uniqueMember is a MAY). I therefore assume that Atlassian has simply not tested Crowd with all relevant servers. Nice to see that ApacheDS is part of their integration tests. Greetings from Bremen, Stefan