On 25 Apr 2013, at 15:03, "Zachary, Carlton - Hoboken"
wrote:
> Thanks David.
>
> -Original Message-
> From: david.suarezde...@telefonica.es
> [mailto:david.suarezde...@telefonica.es]
> Sent: Thursday, April 25, 2013 9:35 AM
> To: perl-ldap@perl.org
Thanks David.
-Original Message-
From: david.suarezde...@telefonica.es [mailto:david.suarezde...@telefonica.es]
Sent: Thursday, April 25, 2013 9:35 AM
To: perl-ldap@perl.org
Subject: Re: Net::LDAP Search Filter
Hi there, Carlton,
The problem is that you are asking for employee types x
Thanks Graham.
-Original Message-
From: Graham Barr [mailto:gb...@pobox.com]
Sent: Thursday, April 25, 2013 9:31 AM
To: Zachary, Carlton - Hoboken
Cc: perl-ldap@perl.org
Subject: Re: Net::LDAP Search Filter
On Apr 25, 2013, at 08:26 , "Zachary, Carlton - Hoboken"
wrote:
&
en"
Para:
"perl-ldap@perl.org"
Fecha:
25/04/2013 15:27
Asunto:
Net::LDAP Search Filter
Hello all,
I am trying to run this search against my directory service with the
following filter and it returns nothing.
(&(employeetype=x)(employeetype=y)(objectclass=*))
But if I
On Apr 25, 2013, at 08:26 , "Zachary, Carlton - Hoboken"
wrote:
> Hello all,
>
> I am trying to run this search against my directory service with the
> following filter and it returns nothing.
>
> (&(employeetype=x)(employeetype=y)(objectclass=*))
that is checking
(employeetype=x) and (emp
Hello all,
I am trying to run this search against my directory service with the following
filter and it returns nothing.
(&(employeetype=x)(employeetype=y)(objectclass=*))
But if I do just:
(&(employeetype=x)(objectclass=*))
Or
(&(employeetype=y)(objectclass=*))
I get search data returned.
2011/7/27 Peter Marschall :
> Hi,
>
> On Wednesday, 20. July 2011, Graham Barr wrote:
>> On Jul 20, 2011, at 07:32 , Francis Swasey wrote:
>> > On Jul 20, 2011, at 8:26, Chris Ridd wrote:
>> >> Graham, should _escape be made public? It seems like it would be useful.
>> > Perhaps a flag on the new
Hi,
On Wednesday, 20. July 2011, Graham Barr wrote:
> On Jul 20, 2011, at 07:32 , Francis Swasey wrote:
> > On Jul 20, 2011, at 8:26, Chris Ridd wrote:
> >> Graham, should _escape be made public? It seems like it would be useful.
> > Perhaps a flag on the new call that indicates there are no esca
2011/7/20 Chris Ridd :
>
> On 20 Jul 2011, at 13:36, Graham Barr wrote:
>
>>
>> On Jul 20, 2011, at 07:32 , Francis Swasey wrote:
>>
>>>
>>>
>>> On Jul 20, 2011, at 8:26, Chris Ridd wrote:
>>>
>
>
>
Graham, should _escape be made public? It seems like it would be useful.
On 20 Jul 2011, at 13:36, Graham Barr wrote:
>
> On Jul 20, 2011, at 07:32 , Francis Swasey wrote:
>
>>
>>
>> On Jul 20, 2011, at 8:26, Chris Ridd wrote:
>>
>>>
>>>
>>> Graham, should _escape be made public? It seems like it would be useful. Or
>>> is manipulating the d
On Jul 20, 2011, at 07:32 , Francis Swasey wrote:
>
>
> On Jul 20, 2011, at 8:26, Chris Ridd wrote:
>
>>
>>>
>>>
>>>
>>
>> Graham, should _escape be made public? It seems like it would be useful. Or
>> is manipulating the data structure returned from new the better approach?
>
> Perhap
On Jul 20, 2011, at 8:26, Chris Ridd wrote:
>
>>
>>
>>
>
> Graham, should _escape be made public? It seems like it would be useful. Or
> is manipulating the data structure returned from new the better approach?
Perhaps a flag on the new call that indicates there are no escapes in the
st
l also escape the other characters that are special
in LDAP search filter strings.
eg: Net::LDAP::Filter::_escape("(cn=foo)") returns '\28cn=foo\29'.
That is because "(" and ")" are special characters.
So you can't usefully run it on the entire filter string
Le 20 juillet 2011 13:13, Chris Ridd a écrit :
>
> On 20 Jul 2011, at 11:34, Clément OUDOT wrote:
>
>> Hi,
>>
>> I will have a look to Net::LDAP::Filter, but I see in Net::LDAP that a
>> new Net::LDAP::Filter is created in the search subroutine when filter
>> is a string. Why do the Net::LDAP::Fil
On 20 Jul 2011, at 11:34, Clément OUDOT wrote:
> Hi,
>
> I will have a look to Net::LDAP::Filter, but I see in Net::LDAP that a
> new Net::LDAP::Filter is created in the search subroutine when filter
> is a string. Why do the Net::LDAP::Filter object do not escape the
> special characters from t
I added this line :
>>
>> $searchFilter =~ s/\\//;
>>
>>
>> My question: is this a bug in my code, or can this be a Perl-LDAP bug?
>> I am using version 0.4001.
>
> I think it is a bug in your code :-(
>
> LDAP search filter strings consider cert
ackslash ('\'). This is the case for example if the value
> is a DN like this : cn=OUDOT\, Clement, ou=users, dc=example, dc=com
>
> To make this works, I added this line :
>
> $searchFilter =~ s/\\//;
>
>
> My question: is this a bug in my code, or can this
Hi,
I have a piece of code where I build a search filter with some
variables, like this:
my $searchFilter =
"(&(objectClass=" . $portal->{ldapGroupObjectClass} . ")(|";
foreach ( split( $portal->{multiValuesSeparator}, $value ) ) {
$searchFilter .= "(" . $key . "=" . $_ . ")
On 19/1/05 8:09 pm, sharib <[EMAIL PROTECTED]> wrote:
>
>
> Hi,
>
> I am having a weird problem with the ldap search filter. Here it is
>
> when using the filter (&(Title=training*)(Owner=*e7001*)), i get 1
> result out of the total of 2 entries that i sho
Original Message
Subject: ldap search filter
From:"sharib" <[EMAIL PROTECTED]>
Date:Wed, January 19, 2005 2:05 pm
To: [EMAIL PROTECTED]
-
Hi,
I am having a weird problem with the ldap search filter. Here it is
when using the filter (&(Title=training*)(Owner=*e7001*)), i get 1
result out of the total of 2 entries that i should get. One entry that
is being missed is however returned when the use the following filter
(&am
On 10/12/03 11:17 pm, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
> Hey,
>
> I tried by authenticating as the root but it still fails.I checked the
> config files and it ssays that read on all attributes is allowed for al
> lusers.
>
> I cant understand why just the and operator is failing desp
Hey,
I tried by authenticating as the root but it still fails.I checked the
config files and it ssays that read on all attributes is allowed for al
lusers.
I cant understand why just the and operator is failing despite any
restrictions.
Any clues
sharib
t; into your perl code. The reverse might not work because Net::LDAP is more
> > forgiving about missing outer ()s than ldapsearch.
> >
> > --Jim Harle
> >
> > On Fri, 5 Dec 2003, Graham Barr wrote:
> >
> > > Begin forwarded message:
> > >
iving about missing outer ()s than ldapsearch.
>
> --Jim Harle
>
> On Fri, 5 Dec 2003, Graham Barr wrote:
>
> > Begin forwarded message:
> > > From: [EMAIL PROTECTED]
> > > Date: 5 December 2003 22:23:49 GMT
> > > To: [EMAIL PROTECTED]
> > >
o your perl code. The reverse might not work because Net::LDAP is more
forgiving about missing outer ()s than ldapsearch.
--Jim Harle
On Fri, 5 Dec 2003, Graham Barr wrote:
> Begin forwarded message:
> > From: [EMAIL PROTECTED]
> > Date: 5 December 2003 22:23:49 GMT
> > T
Begin forwarded message:
From: [EMAIL PROTECTED]
Date: 5 December 2003 22:23:49 GMT
To: [EMAIL PROTECTED]
Subject: ldap search filter problem
Message-Id: <[EMAIL PROTECTED]>
Hi,
I am having trouble doing a existing filter search on my LDAP
directory.
My LDAP directory is openLDAP v3 server
27 matches
Mail list logo
