Re: [DN] Existing API review

Matthew Swift a écrit : public DN(String dnStr) { return valueOf( dnStr ); } Nothing will prevent you from writing something like that, but the compiler will prevent you from compiling it. Get some sleep! ;-) Doh !!! Yeah, or maybe some stronger coffee ;) -- Regards, Cordialement,

Control wiki page

Hi, I have added this page on the wiki : http://cwiki.apache.org/confluence/display/DIRAPI/Control -- Regards, Cordialement, Emmanuel Lécharny www.nextury.com

Re: About the Control interface

Matthew Swift a écrit : snip/ GenericControl(String oid) // non-critical, null value GenericControl(String oid, boolean isCritical) // null value Makes sense to add this constructor, but for Control with *no* value (semantically more accurate, compared to *null* value).

Entry API

Hi, here are some preliminary thoughts about the Entry class. The Entry class --- It's the base data structure representing an element stored into a LDAP server. It has a name (a DN) and some attributes. All the existing API use the same name, Entry (or LDAPEntry), except JNDI

Handling M$ specification violations

Hi, M$, as usual, is violating many LDAP RFCs. For instance, you can send a simple BindRequest where the user name is *not* a DN. I guess we will have to bend the API to accept such crapity... wdyt ? curseM$/curse -- Regards, Cordialement, Emmanuel Lécharny www.nextury.com

About exceptions

Hi, it's about time to talk about exceptions, as many methods will throw an exception, and it would be good to know what to throw ! We should first have a base exception, and I suggest using LdapException. Evey other exception will inherit this one. The second point is that the LDAP

Immutable objects, what's best ?

Hi, we have many objects that we want to be immutable. What's the best solution to produce those immutable objets ? - For DN, we would like to use valueOf(), and the DN() constructor, but no setter - For Entry, a constructor is not enough, as we may have to inject new attributes. We may need to

Re: Immutable objects, what's best ?

On 3/14/10 9:46 AM, Stefan Seelmann wrote: Emmanuel Lecharny schrieb: Hi, we have many objects that we want to be immutable. What's the best solution to produce those immutable objets ? - For DN, we would like to use valueOf(), and the DN() constructor, but no setter - For Entry

Re: About exceptions

On 3/14/10 10:56 AM, Kiran Ayyagari wrote: from the recent experience of migrating test cases to client-api have observed that unlike jndi we return result codes and I liked this (the jndi exceptions rather give me a feeling like 'use exceptions for control flow', which is considered as a bad

Re: Problems to do a search

On 5/12/10 1:07 PM, Juan Luis Hidalgo Vera wrote: Hi, We've found a problem when we do a search with a filter with * in the start or in the end of a expression with wildcards chars like for example filter (uid=*se*). Sounds like a bug ! Can you open a JIRA for that ? OTOH, you have to

About operation result

Hi, long time, no see :) I have a proposal about the way we handle the operation results. Currently, every operation is returning a Response, and if we want to know if the operation has been successful, we have to check the LdapResult field. This is not very convenient. Assuming that when

Twitter for ApacheDS

Hi ! just to inform you guys that we have created a twitter account (twitter.com/apacheDS) where we will put some relevant infos (well, we hope they will be relevant ;). -- Regards, Cordialement, Emmanuel Lécharny www.iktek.com

Re: [Shared] API Design Questionnaire #1

On 1/30/11 7:07 PM, Alex Karasulu wrote: On Sun, Jan 30, 2011 at 7:29 PM, Stefan Seelmannseelm...@apache.orgwrote: On Sun, Jan 30, 2011 at 5:11 PM, Alex Karasuluakaras...@apache.org wrote: On Sun, Jan 30, 2011 at 3:17 AM, Emmanuel Lecharnyelecha...@gmail.com wrote: On 1/29/11 10:38 PM,

Re: LdapConnection threadsafe?

On 4/11/11 8:26 AM, Luis Pérez wrote: Hi, Is the LdapConnection object threadsafe? It's supposed to be. You should be able to send a SearchRequest and an AbandonRequest through the same connection, and see your searchRequest abandonned (if it's a long one, of course. Can I perform two

[ANNOUNCE] Apache LDAP API 1.0.0-M3 has been released !

The Apache Directory team is proud to announce the availability of the 1.0.0-M3 version of the Apache Directory LDAP API. The Apache LDAP client API is an ongoingeffort to provide an enhanced LDAP API, as a replacement for JNDI and the existing LDAP API (jLdap and Mozilla LDAP API). This is

Re: startTLS hostname verification

On 1/20/12 9:14 PM, Daniel Fisher wrote: Looking over the API I don't see an obvious way to perform hostname verification after the SSL handshake. Is this currently possible? I have to check that. It should be possible, as it's a part of the underlying MINA layer, but we may not expose this

[ANNOUNCE] Apache Directory LDAP API 1.0.0-RC1 released

The Apache Directory Team is proud to announce the availability of version 1.0.0-RC1 of the Apache Directory LDAP API. The Apache Directory LDAP API is an ongoing effort to provide an enhanced LDAP API, as a replacement for JNDI and the existing LDAP API (jLdap and Mozilla LDAP API). This is a

LDAP API 1.0-RC2 release coming soon

Hi guys, I have started working n cutting a release for LDAP API. There is not much I want to do for this release, which is quite importat because it depends on MINA 2.0.15, which contains a critical SSL fix. Otherwise, here are some JIRAs I want to address for this release : * DIRAPI-259 :

LDAPConnection fixes

Hi ! Stefan has added some TODO in the LdapConnection interface : // TODO: all the SASL bind methods are not declared in this interface, but implemented in LdapNetworkConnection. Is that intended? // TODO: why does connect() return a boolean? What is the difference between false and an

Re: Immutable SyntexCheckers

Thanks, Stefan. I'll have a look at generics tonite. Regarding the need of a builder for each class, I think it would help habing a consistent system across all the SCs. Otherwise, this idea should apply to the other schema objects. Le dim. 19 mars 2017 à 10:58, Stefan Seelmann

Re: Ldap API Custom Controls

It's a bit tricky... What control do you want to implement? Do you have a description ? Le dim. 3 sept. 2017 à 15:58, Chris Pike a écrit : > Hi, > > I am trying to add a custom control. I started by creating a class that > implements

Re: Fast openldap schema parser : completed

ultra convenientt, and does not put us > at risk. > - The code has been pushed in the API 2.0 branch. > > I haven't yet tested Studio with this new code, this is soemthing I'll > do soon. > > Hope you'll find that convenient ! > -- > Emmanuel Lecharny > > Symas.com > directory.apache.org > >

[ANNOUNCE] Apache LDAP API 2.0.0AM2 released

The Apache Directory Team is proud to announce the availability of version 2.0.0.AM2 of the Apache Directory LDAP API, the second milestone toward a 2.0 version of the Apache LDAP API The Apache Directory LDAP API is an ongoing effort to provide an enhancedLDAP API, as a replacement for JNDI and

[Announcement] Apache LDAP API 1.0.2 released

The Apache Directory Team is proud to announce the availability of version 1.0.2 of the Apache Directory LDAP API. The Apache Directory LDAP API is an ongoing effort to provide an enhancedLDAP API, as a replacement for JNDI and the existing LDAP API (jLdap and Mozilla LDAP API). This is a schema

[Annoucement] CVE-2018-1337 Plaintext Password Disclosure in Secured Channel

CVE-2018-1337: Plaintext Password Disclosure in Secured Channel Severity: Critical Vendor: The Apache Software Foundation Versions Affected: Apache LDAP API 1.0.0 Description: A bug in the way the SSL Filter was setup made it possible for another thread to use the connection before the TLS

[Announcement] : Apache LDAP API 1.0.2

The Apache Directory LDAP API is an ongoing effort to provide an enhancedLDAP API, as a replacement for JNDI and the existing LDAP API (jLdap and Mozilla LDAP API). This is a schema aware API, with some convenient ways to access a LDAP server. This API is not only targeting the Apache Directory

Re: Qustion regarding schema quirk mode

That will be when I’ll be back from vacations :-) Le lun. 23 avr. 2018 à 12:40, Radovan Semancik < radovan.seman...@evolveum.com> a écrit : > Hi, > > As far as I remember it should also contain: > > * Allow (pretty much any) string as OID. E.g. "whatever-oid" is often > used instead of real OID

[ANNOUNCE] Apache Directory LDAP API 2.0.0.AM4 released

The Apache Directory Team is proud to announce the availability of version 2.0.0.AM4 of the Apache Directory LDAP API, the forth milestone toward a 2.0 version of the Apache LDAP API. The Apache Directory LDAP API is an ongoing effort to provide an enhanced LDAP API, as a replacement for JNDI and

Re: NPE in ERR_04122_SSL_CONTEXT_INIT_FAILURE Failed to initialize the SSL context

t; to not end? > > > > [1] https://github.com/apache/guacamole-client > > [2] https://github.com/michaelbarkdoll/guacamole-client/tree/jira/234 > > [3] > > https://gist.github.com/michaelbarkdoll/d78614635fa0432ab08100d05f1a4919 > > > > Michael Barkdoll >

Re: NPE in ERR_04122_SSL_CONTEXT_INIT_FAILURE Failed to initialize the SSL context

4919 > > Michael Barkdoll > > > > On Fri, Apr 26, 2019 at 12:26 AM Stefan Seelmann > wrote: > > > On 4/26/19 7:09 AM, Emmanuel Lecharny wrote: > > >> ERR_04122_SSL_CONTEXT_

[Announcement] : Apache LDAP API 2.1.4

The Apache Directory project is proud to announce the release of the Apache LDAP API 2.1.4 version ! The Apache Directory LDAP API is an ongoing effort to provide an enhanced LDAP API, as a replacement for JNDI and the existing LDAP API (jLdap and Mozilla LDAP API). This is a schema aware API,

[Announcement] : Apache LDAP API 2.1.2

he Apache Directory project is proud to announce the release of the Apache LDAP API 2.1.2 version ! The Apache Directory LDAP API is an ongoing effort to provide an enhanced LDAP API, as a replacement for JNDI and the existing LDAP API (jLdap and Mozilla LDAP API). This is a schema aware API,

[Announcement] : Apache LDAP API 2.1.1

The Apache Directory project is proud to announce the release of the Apache LDAP API 2.1.1 version ! The Apache Directory LDAP API is an ongoing effort to provide an enhanced LDAP API, as a replacement for JNDI and the existing LDAP API (jLdap and Mozilla LDAP API). This is a schema aware API,