[ldapext] support for Assertion Control

Michael Ströder <michael@stroeder.com> Wed, 13 January 2016 13:50 UTC

Return-Path: <michael@stroeder.com>
X-Original-To: ldapext@ietfa.amsl.com
Delivered-To: ldapext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 7FB351B2DCD for <ldapext@ietfa.amsl.com>; Wed, 13 Jan 2016 05:50:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.903
X-Spam-Status: No, score=-0.903 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id CMZzQGtGIsQB for <ldapext@ietfa.amsl.com>; Wed, 13 Jan 2016 05:50:19 -0800 (PST)
Received: from srv1.stroeder.com (srv1.stroeder.com []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 139911B2DC6 for <ldapext@ietf.org>; Wed, 13 Jan 2016 05:50:19 -0800 (PST)
Received: from srv4.stroeder.local (unknown []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.stroeder.local", Issuer "stroeder.com Server CA no. 2009-07" (verified OK)) by srv1.stroeder.com (Postfix) with ESMTPS id DFF8E1CEBD for <ldapext@ietf.org>; Wed, 13 Jan 2016 13:50:16 +0000 (UTC)
Received: from nb2.stroeder.local (nb2.stroeder.local []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by srv4.stroeder.local (Postfix) with ESMTPS id 440211D311 for <ldapext@ietf.org>; Wed, 13 Jan 2016 13:50:15 +0000 (UTC)
To: ldapext <ldapext@ietf.org>
From: Michael Ströder <michael@stroeder.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <56965616.60507@stroeder.com>
Date: Wed, 13 Jan 2016 14:50:14 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:42.0) Gecko/20100101 SeaMonkey/2.39
MIME-Version: 1.0
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="------------ms030902050904070203040508"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ldapext/aboBke-72Xm2xHSZPa0Rh0oECgw>
Subject: [ldapext] support for Assertion Control
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ldapext>, <mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ldapext/>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ldapext>, <mailto:ldapext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jan 2016 13:50:21 -0000


I need to do some interop-testing for a work-around in case an Assertion Control
[1] is sent along with modify requests. I currently only know two LDAP servers
supporting it:

Any other LDAP servers supporting [1] which I should test with?
Do they have attribute 'entryDN' [2] in their entries and support for at least
EQUALITY matching?

Ciao, Michael.

[1] https://tools.ietf.org/html/rfc4528
[2] https://tools.ietf.org/html/rfc5020