Return-Path: X-Original-To: apmail-directory-users-archive@www.apache.org Delivered-To: apmail-directory-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B2B8817C8A for ; Fri, 18 Sep 2015 13:39:08 +0000 (UTC) Received: (qmail 3510 invoked by uid 500); 18 Sep 2015 13:39:02 -0000 Delivered-To: apmail-directory-users-archive@directory.apache.org Received: (qmail 3464 invoked by uid 500); 18 Sep 2015 13:39:02 -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 3445 invoked by uid 99); 18 Sep 2015 13:39:02 -0000 Received: from Unknown (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Sep 2015 13:39:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 89078C0707 for ; Fri, 18 Sep 2015 13:39:01 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.121 X-Spam-Level: X-Spam-Status: No, score=-0.121 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id dAFZgFMCCXyk for ; Fri, 18 Sep 2015 13:39:00 +0000 (UTC) Received: from mail-pa0-f46.google.com (mail-pa0-f46.google.com [209.85.220.46]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id E888042B0A for ; Fri, 18 Sep 2015 13:38:59 +0000 (UTC) Received: by pacex6 with SMTP id ex6so52071764pac.0 for ; Fri, 18 Sep 2015 06:38:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-type:content-transfer-encoding; bh=AVyUFsQChBWl/HWUjm0dGLyfQguWG9rqnLBReU7nMvw=; b=sIbN4yAZqFIxgO4zgO3LLP7ui+AU1IqtVh/GMLDHh/NyKRZsdSvmAhMzPRV4lLHA7M oycVOHbsNrdO5E+ER1Gz/7boVqgp/Gn+tHyo2obgvenp+sjGnOmTz578Ma+2su/DD/ir pPr7GeGF2GSgl9nPlX7+tiXfxwiFgYKPfys/T/hVuSTZ2IkdCvZM6H5z0JcXPnkyjE9J OoJEvBn1iDG+57dEMbJJXR5N2nDnbaMoDqVKmoYDcKdnR9k0XsX9TtkAITLIHDtvddxv xZoBv0xRdBr8V3CXjrVPeeMJYU620wKvJ3GR/Fl9enlYxf1Et6rxRrB1PY/8Da0JXwp+ s1Sg== X-Received: by 10.68.68.233 with SMTP id z9mr7454517pbt.132.1442583533688; Fri, 18 Sep 2015 06:38:53 -0700 (PDT) Received: from [192.168.1.29] (195.232.99.84.rev.sfr.net. [84.99.232.195]) by smtp.googlemail.com with ESMTPSA id ch3sm9209422pbb.18.2015.09.18.06.38.52 for (version=TLSv1/SSLv3 cipher=OTHER); Fri, 18 Sep 2015 06:38:53 -0700 (PDT) Subject: Re: Question about fetching attributes To: users@directory.apache.org References: <55FBF9D0.10901@gaianconsultants.com> From: =?UTF-8?Q?Emmanuel_L=c3=a9charny?= Message-ID: <55FC13EB.20709@gmail.com> Date: Fri, 18 Sep 2015 15:38:51 +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: <55FBF9D0.10901@gaianconsultants.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Le 18/09/15 13:47, Syed Mudassir a écrit : > Hi Everybody, > I am able to connect to Windows Active Directory. I am able to lookup an > object and get the attributes. However, this is the problem I am facing. > Suppose an entry has 'm' attributes out of which 'n' attributes are assigned > values. The remaining attributes are simply unassigned. > When I do search or lookup operation, I am getting only 'n' attributes > listed. I need the reamining (m-n) attributes as well. > Anyone can help how to do that? The list of attributes that an entry can contain is available in the combinaison of ObjectClasses this entry is subject to. Two things though : - ObjectClasses can inherit from some other ObjectClasses, and those parent ObjectClasses may not be present in teh Entry. You will have to know about them on the client side - if one of the ObjectClass is extensibleObject, then the entry may contain *any* attribute, even some that the server does not support. In any case, your client application must have some knowledge about your LDAP server schema. Otherwise, any reason you need to know which are the missing attributes ?