Mailing-List: contact users-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@directory.apache.org
Subject: Re: Get all attributes
To: users@directory.apache.org
References: <5DFC4187-7300-4E04-94FF-871C16F391B1@icloud.com>
 <F1B58BE6-CD12-4DE4-A467-2D90EC6331D1@icloud.com>
 <CABzFU-cJdKen-xNxOkLqX1fBv62T5O+_2Ode_tKoaKn=gAVykQ@mail.gmail.com>
 <524A76C2-6EE5-415E-B944-16D31048B39E@icloud.com> <56005626.70905@gmail.com>
 <E13DAF01-9A07-40E9-83A5-A2921632BD31@icloud.com>
 <5603F2C3.7020700@gmail.com>
 <416BC3E6-C555-4CCD-AEA9-3DE71D9C723D@icloud.com>
From: =?UTF-8?Q?Emmanuel_L=c3=a9charny?= <elecharny@gmail.com>
Message-ID: <56040181.5020507@gmail.com>
Date: Thu, 24 Sep 2015 15:58:25 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0)
 Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <416BC3E6-C555-4CCD-AEA9-3DE71D9C723D@icloud.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit

Le 24/09/15 15:19, Syed Mudassir Ahmed a écrit :
> This solution applies to Windows active directory. For each value of objectClass (top, person, etc) there is an object in cn=schema,cn=configuration,dc=... . Each of these objects tells required and optional attributes. For the given entry, get all the values of its objectClass and query those objects for attributes.
yes, but this is not the solution to the very question you asked. Here,
what you are doing is that you fetch the schema, and then you deduce the
optional AttributeTypes a specific entry can have by checking for its
ObjectClasses.

Your question was "When I do search or lookup operation, I am getting
only 'n' attributes listed. I need the reamining (m-n) attributes as
well." and the short answer is : you can't. It's a two step operation,
actually...

Now, yes, fecthing the schema is the way to go, and you have to store
the information locally. The LDAP API can do that, so you won't need to
specifically request for the information every tilme you fecth an entry.
(although for AD, this is a bt more complex than just fetching teh
schema, just because AD is not implementng LDAP the way it should ;-)