Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 80423200CF0 for ; Thu, 7 Sep 2017 22:21:36 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 7EAE9160E1C; Thu, 7 Sep 2017 20:21:36 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id CD4B7160C89 for ; Thu, 7 Sep 2017 22:21:35 +0200 (CEST) Received: (qmail 59277 invoked by uid 500); 7 Sep 2017 20:21:34 -0000 Mailing-List: contact api-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: api@directory.apache.org Delivered-To: mailing list api@directory.apache.org Received: (qmail 59265 invoked by uid 99); 7 Sep 2017 20:21:34 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Sep 2017 20:21:34 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 75F8AC63B1 for ; Thu, 7 Sep 2017 20:21:33 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -1.3 X-Spam-Level: X-Spam-Status: No, score=-1.3 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id Tr1sFrrydU1g for ; Thu, 7 Sep 2017 20:21:29 +0000 (UTC) Received: from tr22g10.aset.psu.edu (tr22g10.aset.psu.edu [146.186.149.133]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 69007612C9 for ; Thu, 7 Sep 2017 20:21:05 +0000 (UTC) Received: from ucs12.ait.psu.edu (ucs12.ait.psu.edu [146.186.15.96]) by tr22g10.aset.psu.edu (8.15.2/8.15.2) with ESMTP id v87KKxc033161222 for ; Thu, 7 Sep 2017 16:20:59 -0400 Date: Thu, 7 Sep 2017 16:20:58 -0400 (EDT) From: Chris Pike To: api Message-ID: <1226264384.1941056.1504815658976.JavaMail.zimbra@psu.edu> In-Reply-To: <2140643619.370609.1504565437966.JavaMail.zimbra@psu.edu> References: <473683107.34496.1504447116171.JavaMail.zimbra@psu.edu> <2074099317.91140.1504465076697.JavaMail.zimbra@psu.edu> <7a4afa4b-5b66-7787-3730-77bc080a7916@gmail.com> <2140643619.370609.1504565437966.JavaMail.zimbra@psu.edu> Subject: Re: Ldap API Custom Controls MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Originating-IP: [128.118.110.68] X-Mailer: Zimbra 8.7.7_GA_1787 (ZimbraWebClient - FF55 (Linux)/8.7.7_GA_1787) Thread-Topic: Ldap API Custom Controls Thread-Index: DmlCLHArOC6fF00BXaq3P+oSCxiiuZTbFshT X-Virus-Scanned: by amavisd-new archived-at: Thu, 07 Sep 2017 20:21:36 -0000 So I added the controls, but they don't seem to be working. We are getting = a error code 53 (unwilling to preform) when we add the control to our reque= st, so assuming there is something wrong with the control, but don't know e= nough about ldap or the library to know what. Any ideas on what to try or w= hat might be wrong? ----- Original Message ----- From: "Chris Pike" To: "api" Sent: Monday, September 4, 2017 6:50:37 PM Subject: Re: Ldap API Custom Controls Thanks for the suggestions and code examples. I'll work on adding this new = control and let you know if I have any issues. ~Chris Pike ----- Original Message ----- From: "Emmanuel L=C3=A9charny" To: "api" Sent: Monday, September 4, 2017 3:46:49 AM Subject: Re: Ldap API Custom Controls Le 04/09/2017 =C3=A0 09:16, Radovan Semancik a =C3=A9crit=C2=A0: > On 09/04/2017 09:02 AM, Emmanuel L=C3=A9charny wrote: >> Actually, the tricky part is the grammar, which is a state engine >> description. > > Oh, that is usually not that difficult either. Most of those "custom" > controls are very simple. Just a couple of fields. Complex data > structures seem to be very rare. If you start with existing control > that is somehow similar it is not difficult to implement a new control. FTR, the code I provided yesterday night in one of my previous mail took me around 30 mins, all included. For a more complex control, like syncrepl, that would have takne a bit more time, mainly because you want to add unit tests to cover teh various cases. Now, I think that we should provide a bit of documentation about how to implement a control... --=20 Emmanuel Lecharny Symas.com directory.apache.org