perl-ldap-dev

LDAP v3

[ritu r. j. <lin...@re...>]

can u please tell me where to get the information regarding 

the differences between LDAP Version 2 and LDAP Version 3 

thanks in advance.

ritu

_____________________________________________________
Chat with your friends as soon as they come online. Get Rediff Bol at
http://bol.rediff.com

Participate in crazy auctions at http://auctions.rediff.com/auctions/

Re: Greek characters - Utf8 encoding.

[Graham B. <gb...@po...>]

On Tue, Nov 21, 2000 at 01:33:46PM +0000, Chris Ridd wrote:
> So since Net::LDAP is character-set agnostic, it handles UTF-8 values OK.
> What you do with the bytes of the value once you get them from Net::LDAP is
> up to you. Presumably there are ways in perl 5.6 to convert a string full
> of bytes which happen to be a UTF-8 representation of a string into a
> string which is interpreted by perl as UTF-8. I seem to recall that perl
> 5.6 has ways to do these conversions.

In 5.6 (if Net::LDAP will work with 5.6) the strings should be returned as
UTF8 IIRC.

Graham.

Re: Testing for missing attributes

[<Sim...@wi...>]

This may well be my understanding at fault ;-)

      What I am testing for is when a user last logged in.

      It seems that Novell doesn't actually create an attribute of loginTime (or
      lastLoginTime) until a user has logged in for the first time.

      So when I test my $entry->get('loginTime') I get undef, i.e. there is no
      attribute loginTime.

      Looking in the debug traces it seems that the attribute is not returned by
      the server.

      I've seen this behaviour from Novell when a user does not have rights to
      an attribute.

      I would have expected that the attribute would exist even if it was a zero
      length string.

      In that case, $entry->get('loginTime') should return an array ref, the
      first element of which was zero length.

      Does that make sense ?

      Anyway, I've managed to get around the problem (with an appropriate search
      filter) so this is now just a user (i.e. me) education issue now :-)

      Thanks to all for their help.

      Cheers,

      Simon Wilcox.






               From           Chris Ridd <chr...@me...>
  Date   21 November 2000
                                                                            
                                                                            
        To                                                                  
                Simon Wilcox/BASE/WilliamsLea@WilliamsLea,  Time  14:15     
                per...@li...                         
                                                                            


      Copy to



      Bcc



      Fax to



      Subject       Re: Testing for missing attributes





Sim...@wi... wrote:
>       It seems that Novell does not return an attribute at all rather
>       than an attribute that has a null value.

I'm not quite sure what this means.

It is not legal in LDAP to have an attribute with no values. Some
attributes have syntaxes which support values which are zero-length
strings, which is *not* the same as 'no value'. (Example: distinguished
names can be zero-length, ie the root has a string DN of "".)

Cheers,

Chris









______________________________________________________________________


   This email contains proprietary information some or all of which may be
   legally privileged.  It is for the intended recipient only. If an addressing
   or transmission error has misdirected this email, please notify the author by
   replying to this email. If you are not the intended recipient you must not
   use, disclose, distribute, copy, print, or reply on this email.

Re: Testing for missing attributes

[Chris R. <chr...@me...>]

Sim...@wi... wrote:
>       It seems that Novell does not return an attribute at all rather
>       than an attribute that has a null value.

I'm not quite sure what this means.

It is not legal in LDAP to have an attribute with no values. Some
attributes have syntaxes which support values which are zero-length
strings, which is *not* the same as 'no value'. (Example: distinguished
names can be zero-length, ie the root has a string DN of "".)

Cheers,

Chris

Re: Greek characters - Utf8 encoding.

[Chris R. <chr...@me...>]

James Chang <Jam...@ms...> wrote:
> Hi (guys), would someone please give me a definitive answer as to whether
> Net::LDAP 0.22 handles Utf 8?

Net::LDAP doesn't care what characters are used in attribute values - all
it does is set/get the bytes in scalars (strings.)

> I'm converting some ISO 8859-7 (Greek) characters into their equivalent
> Utf 8 mapping and was hoping (actually kind of depending) on the use of
> an ldap version 3 server to serve as a directory of this information
> (including the distinguished names).  I came across a posting from August
> which suggested that Utf 8 is not handled.  I'm using Perl 5.6 and
> Net::LDAP version 0.22.

Presumably you could also use an LDAPv2 server which implemented character
sets correctly (ie T.61, not UTF-8 or ISO 8859-1), but using UTF-8 and
LDAPv3 is probably easier.

So since Net::LDAP is character-set agnostic, it handles UTF-8 values OK.
What you do with the bytes of the value once you get them from Net::LDAP is
up to you. Presumably there are ways in perl 5.6 to convert a string full
of bytes which happen to be a UTF-8 representation of a string into a
string which is interpreted by perl as UTF-8. I seem to recall that perl
5.6 has ways to do these conversions.

Cheers,

Chris

Re: Testing for missing attributes

[<Sim...@wi...>]

Thanks folks, that got it !

      FWIW, I eventually found that the attribute Novell show as Last Login in
       Console One maps to an LDAP attribute loginTime, not lastLoginTime as you
       might expect :-)

      Anyone know the difference ?

      Simon.



______________________________________________________________________


   This email contains proprietary information some or all of which may be
   legally privileged.  It is for the intended recipient only. If an addressing
   or transmission error has misdirected this email, please notify the author by
   replying to this email. If you are not the intended recipient you must not
   use, disclose, distribute, copy, print, or reply on this email.

ILS servers?

[Brian S. <br...@me...>]

Has anyone seen any code about that specifically accesses ILS servers using
the Perl-LDAP modules ( this is the Microsoft LDAP type server that is used
as a location function for NetMeeting)?

Greek characters - Utf8 encoding.

[James C. <Jam...@ms...>]

Hi (guys), would someone please give me a definitive answer as to whether
Net::LDAP 0.22 handles Utf 8?

I'm converting some ISO 8859-7 (Greek) characters into their equivalent Utf
8 mapping and was hoping (actually kind of depending) on the use of an ldap
version 3 server to serve as a directory of this information (including the
distinguished names).  I came across a posting from August which suggested
that Utf 8 is not handled.  I'm using Perl 5.6 and Net::LDAP version 0.22.

If not is there another way to do this using any other Perl LDAP module that
anyone's come across?  I did have a browse through CPAN but didn't find
anything else not related to Net::LDAP.

Thanks for your attention.

Re: Handling session authentication in a web app

[Mark W. <mew...@un...>]

No there's not a simple way of testing permissions before attempting an operation.

Mark

Tom Jordan wrote:

> That's the conclusion I'm coming to. I'm working on storing session state
> in a local database (along with encrypted username/password data).
>
> Different question (but along the same lines):
>
> Is there a way to test whether an attribute is writeable by the current
> user? I'd like to simply display all attributes that a user has rights to
> view and supply an option to edit those that may be written. Is there a
> way to determine which is which short of attempting to write (and
> failing)?
>
> Thanks,
> Tom
>
> On Mon, 20 Nov 2000, Mark Wilcox wrote:
>
> > if you want to use permissions as they are stored in the LDAP server for
> > LDAP operations (not a bad idea because that way users have the same rights
> > regardless of how they interact with the LDAP server) you need to store the
> > DN and password so that you can keep binding to the server.
> >
> > You either need to store the DN and Password in memory (only possible if
> > you're using mod_perl), in an ecrypted cookie (I use a DES encrypted
> > cookie) or in an encrypted file/database on the server.
> >
> > I don't know of any application that does this in Perl. It's a little bit
> > easier to do this as a Java servlet because it has a default session storage
> > system that's unique per application invocation. You can do the same in Perl,
> > it just takes a bit more work.
> >
> > Mark
> >
> > Tom Jordan wrote:
> >
> > > Hey folks,
> > >
> > > I need to put together a web application to allow people to edit
> > > attributes I've given them access to (password resets for the help desk,
> > > radius info for the network guys, etc).
> > >
> > > I'm pretty clear on what I need to do between the script and the LDAP
> > > server, but does anyone have any suggestions on how to handle session
> > > authentication?
> > >
> > > I'd like to have a client log in to the web app with their uid and
> > > userPassword, and then be able to mess with stuff according to the
> > > permissions given to their object (so the script would bind to the
> > > directory as the user).
> > >
> > > Any suggesions on how to manage the session? Alternately, does anyone know
> > > of any applications like this out there that I could tweak (other than
> > > Netscape's DSGW, which has annoyed me on many occasions).
> > >
> > > Thanks much,
> > >
> > > Tom Jordan
> > > University of Wisconsin Madison
> >

Re: Handling session authentication in a web app

[Tom J. <tj...@do...>]

That's the conclusion I'm coming to. I'm working on storing session state
in a local database (along with encrypted username/password data).

Different question (but along the same lines):

Is there a way to test whether an attribute is writeable by the current
user? I'd like to simply display all attributes that a user has rights to
view and supply an option to edit those that may be written. Is there a
way to determine which is which short of attempting to write (and
failing)?

Thanks,
Tom

On Mon, 20 Nov 2000, Mark Wilcox wrote:

> if you want to use permissions as they are stored in the LDAP server for
> LDAP operations (not a bad idea because that way users have the same rights
> regardless of how they interact with the LDAP server) you need to store the
> DN and password so that you can keep binding to the server.
>
> You either need to store the DN and Password in memory (only possible if
> you're using mod_perl), in an ecrypted cookie (I use a DES encrypted
> cookie) or in an encrypted file/database on the server.
>
> I don't know of any application that does this in Perl. It's a little bit
> easier to do this as a Java servlet because it has a default session storage
> system that's unique per application invocation. You can do the same in Perl,
> it just takes a bit more work.
>
> Mark
>
> Tom Jordan wrote:
>
> > Hey folks,
> >
> > I need to put together a web application to allow people to edit
> > attributes I've given them access to (password resets for the help desk,
> > radius info for the network guys, etc).
> >
> > I'm pretty clear on what I need to do between the script and the LDAP
> > server, but does anyone have any suggestions on how to handle session
> > authentication?
> >
> > I'd like to have a client log in to the web app with their uid and
> > userPassword, and then be able to mess with stuff according to the
> > permissions given to their object (so the script would bind to the
> > directory as the user).
> >
> > Any suggesions on how to manage the session? Alternately, does anyone know
> > of any applications like this out there that I could tweak (other than
> > Netscape's DSGW, which has annoyed me on many occasions).
> >
> > Thanks much,
> >
> > Tom Jordan
> > University of Wisconsin Madison
>

Re: Handling session authentication in a web app

[Mark W. <mew...@un...>]

if you want to use permissions as they are stored in the LDAP server for
LDAP operations (not a bad idea because that way users have the same rights
regardless of how they interact with the LDAP server) you need to store the
DN and password so that you can keep binding to the server.

You either need to store the DN and Password in memory (only possible if
you're using mod_perl), in an ecrypted cookie (I use a DES encrypted
cookie) or in an encrypted file/database on the server.

I don't know of any application that does this in Perl. It's a little bit
easier to do this as a Java servlet because it has a default session storage
system that's unique per application invocation. You can do the same in Perl,
it just takes a bit more work.

Mark

Tom Jordan wrote:

> Hey folks,
>
> I need to put together a web application to allow people to edit
> attributes I've given them access to (password resets for the help desk,
> radius info for the network guys, etc).
>
> I'm pretty clear on what I need to do between the script and the LDAP
> server, but does anyone have any suggestions on how to handle session
> authentication?
>
> I'd like to have a client log in to the web app with their uid and
> userPassword, and then be able to mess with stuff according to the
> permissions given to their object (so the script would bind to the
> directory as the user).
>
> Any suggesions on how to manage the session? Alternately, does anyone know
> of any applications like this out there that I could tweak (other than
> Netscape's DSGW, which has annoyed me on many occasions).
>
> Thanks much,
>
> Tom Jordan
> University of Wisconsin Madison

Re: Testing for missing attributes

[<jo...@pt...>]

Hi, what you probably want is 

(& (objectclass=inetOrgPerson) (!(lastLoginTime=*)))


Works over here, openldap2. 



Sim...@wi... wrote:
> 
> Hi,
> 
>       I am struggling with composing a filter and I hope someone on the list can
>        point me in the right direction.
> 
>       I am using Net::LDAP v0.19, perl 5.005_03 against Novell eDirectory
> 
>       The script I am working on is to display a list of users who have never
>        logged on to the network.
> 
>       This is stored in the LDAP attribute lastLoginTime in eDirectory.
> 
>       If I make the filter (& (objectclass=inetOrgPerson) (lastLoginTime=*)) I
>        get a list of the users who have logged in.
> 
>       Can I somehow reverse this so that I get a list of those who do NOT have a
>        lastLoginTime attribute ?
> 
>       I tried the obvious (& (objectclass=inetOrgPerson) (lastLoginTime!=*)) but
>        that just died with a "Bad filter" error.
> 
>       It seems that Novell does not return an attribute at all rather than an
>        attribute that has a null value.
> 
>       My workaround is just to get all the users and then test for the attribute
>        in the return list but it isn't going to scale very well ;-)
> 
>       All help much appreciated.
> 
>       Rgds,
> 
>       Simon Wilcox
>       Intranet Development Manager
>       Williams Lea Group
> 
> ______________________________________________________________________
> 
>    This email contains proprietary information some or all of which may be
>    legally privileged.  It is for the intended recipient only. If an addressing
>    or transmission error has misdirected this email, please notify the author by
>    replying to this email. If you are not the intended recipient you must not
>    use, disclose, distribute, copy, print, or reply on this email.

Re: Testing for missing attributes

[Mark W. <mew...@un...>]

the NOT, must precede the () just like the AND thus try :
(&(!(lastlogintime=*))(objectclass=inetorgPerson))

mark
Sim...@wi... wrote:

> Hi,
>
>       I am struggling with composing a filter and I hope someone on the list can
>        point me in the right direction.
>

>
>       I am using Net::LDAP v0.19, perl 5.005_03 against Novell eDirectory
>
>       The script I am working on is to display a list of users who have never
>        logged on to the network.
>
>       This is stored in the LDAP attribute lastLoginTime in eDirectory.
>
>       If I make the filter (& (objectclass=inetOrgPerson) (lastLoginTime=*)) I
>        get a list of the users who have logged in.
>
>       Can I somehow reverse this so that I get a list of those who do NOT have a
>        lastLoginTime attribute ?
>
>       I tried the obvious (& (objectclass=inetOrgPerson) (lastLoginTime!=*)) but
>        that just died with a "Bad filter" error.
>
>       It seems that Novell does not return an attribute at all rather than an
>        attribute that has a null value.
>
>       My workaround is just to get all the users and then test for the attribute
>        in the return list but it isn't going to scale very well ;-)
>
>       All help much appreciated.
>
>       Rgds,
>
>       Simon Wilcox
>       Intranet Development Manager
>       Williams Lea Group
>
> ______________________________________________________________________
>
>    This email contains proprietary information some or all of which may be
>    legally privileged.  It is for the intended recipient only. If an addressing
>    or transmission error has misdirected this email, please notify the author by
>    replying to this email. If you are not the intended recipient you must not
>    use, disclose, distribute, copy, print, or reply on this email.

Testing for missing attributes

[<Sim...@wi...>]

Hi,

      I am struggling with composing a filter and I hope someone on the list can
       point me in the right direction.

      I am using Net::LDAP v0.19, perl 5.005_03 against Novell eDirectory

      The script I am working on is to display a list of users who have never
       logged on to the network.

      This is stored in the LDAP attribute lastLoginTime in eDirectory.

      If I make the filter (& (objectclass=inetOrgPerson) (lastLoginTime=*)) I
       get a list of the users who have logged in.

      Can I somehow reverse this so that I get a list of those who do NOT have a
       lastLoginTime attribute ?

      I tried the obvious (& (objectclass=inetOrgPerson) (lastLoginTime!=*)) but
       that just died with a "Bad filter" error.

      It seems that Novell does not return an attribute at all rather than an
       attribute that has a null value.

      My workaround is just to get all the users and then test for the attribute
       in the return list but it isn't going to scale very well ;-)

      All help much appreciated.

      Rgds,

      Simon Wilcox
      Intranet Development Manager
      Williams Lea Group



______________________________________________________________________


   This email contains proprietary information some or all of which may be
   legally privileged.  It is for the intended recipient only. If an addressing
   or transmission error has misdirected this email, please notify the author by
   replying to this email. If you are not the intended recipient you must not
   use, disclose, distribute, copy, print, or reply on this email.

Re: Handling session authentication in a web app

[Yann R. <at...@at...>]

Well, I would do this with a relational database.  Or maybe Apache::Session?

Anyway, here is a perl module which I made awhile back. Its designed to work 
with Postgres and uses some database contraints to make sure the database is 
consistent.  I don't like my old session purging scheme, but hey, it works.
It might help you.

Yann



On Sat, 18 Nov 2000, you (Tom Jordan) might of written:
> Hey folks,
>
> I need to put together a web application to allow people to edit
> attributes I've given them access to (password resets for the help desk,
> radius info for the network guys, etc).
>
> I'm pretty clear on what I need to do between the script and the LDAP
> server, but does anyone have any suggestions on how to handle session
> authentication?
>
> I'd like to have a client log in to the web app with their uid and
> userPassword, and then be able to mess with stuff according to the
> permissions given to their object (so the script would bind to the
> directory as the user).
>
> Any suggesions on how to manage the session? Alternately, does anyone know
> of any applications like this out there that I could tweak (other than
> Netscape's DSGW, which has annoyed me on many occasions).
>
> Thanks much,
>
> Tom Jordan
> University of Wisconsin Madison

-- 

--------------------------------------------------------------------
Yann Ramin			at...@at...
Atrus Trivalie Productions	www.redshift.com/~yramin
AIM				oddatrus
Marina, CA			http://profiles.yahoo.com/theatrus

IRM Developer                   Network Toaster Developer
SNTS Developer                  KLevel Developer
Electronics Hobbyist		person who loves toys

Build a man a fire, and he's warm for a day.
Set a man on fire, and he'll be warm for the rest of his life.

"I'm prepared for all emergencies but totally unprepared for everyday
life." 
--------------------------------------------------------------------

Handling session authentication in a web app

[Tom J. <tj...@do...>]

Hey folks,

I need to put together a web application to allow people to edit
attributes I've given them access to (password resets for the help desk,
radius info for the network guys, etc).

I'm pretty clear on what I need to do between the script and the LDAP
server, but does anyone have any suggestions on how to handle session
authentication?

I'd like to have a client log in to the web app with their uid and
userPassword, and then be able to mess with stuff according to the
permissions given to their object (so the script would bind to the
directory as the user).

Any suggesions on how to manage the session? Alternately, does anyone know
of any applications like this out there that I could tweak (other than
Netscape's DSGW, which has annoyed me on many occasions).

Thanks much,

Tom Jordan
University of Wisconsin Madison

Re: (no subject)

[Chris R. <chr...@me...>]

David Heffernan <dav...@cm...> wrote:
> 
> Hello, i have a little problem that you might be able to help me with.
> 
> I want to look up LDAP for an entry that uses an MSISDN as its key
> attribute. Once i have found the entry i want to change this key
> attribute, and delete the old attribute while keeping the other
> attributes and there values unchanged. 
> 
> I have changed other attributes with a 'modify'    ie      my
> $mesg=$ldap->modify("$WSB_UTIL::WSB_LDAP_USERUID=$oldmsisdn,
> WSB_Util::WSB_UBASE",
>							 changes =>
>							 [
>								 replace =>
> [blocked => yes]
>							 ]);
> 
> Is there an equivalent for the 'modify' if it is the key attribute you are
> modifying.
> 
> Thank you,
> 
> David Heffernan 

You are trying to rename the entry, so use the moddn method and set
deleteoldrdn to false.

Cheers,

Chris

(no subject)

[David H. <dav...@cm...>]

Hello, i have a little problem that you might be able to help me with.

I want to look up LDAP for an entry that uses an MSISDN as its key
attribute. Once i have found the entry i want to change this key attribute,
and delete the old attribute while keeping the other attributes and there
values unchanged. 

I have changed other attributes with a 'modify'    ie      my
$mesg=$ldap->modify("$WSB_UTIL::WSB_LDAP_USERUID=$oldmsisdn,
WSB_Util::WSB_UBASE",
							changes =>
							[
								replace =>
[blocked => yes]
							]);

Is there an equivalent for the 'modify' if it is the key attribute you are
modifying.

Thank you,

David Heffernan 

RE: creating an entry on Exchange

[<jon...@or...>]

Your problem here is that you are not adding all of the objects required by the
"Remote-Address" object class, not which tool set you are using to create them.
Here is what I have used in the past for Exchange 5.5:

		$LDAPConatiner = "cn=Recipients, ou=TEST SITE, o=Test ORG";
		$testfile{$login}{"cn"} = "$lname, $fname";
		$testfile{$login}{"sn"} = "$lname";
		$testfile{$login}{"givenName"} = "$fname";
		$testfile{$login}{"physicalDeliveryOfficeName"} = "$office";
		$testfile{$login}{"telephoneNumber"} = "$phone";
		$testfile{$login}{"department"} = "$department";
		$testfile{$login}{"dn"} = "cn\=\"$lname,
$fname\"\,$LDAPContainer";
		$testfile{$login}{"rdn"} = "$lname, $fname";
		# Keep uid unique so we don't break web access for exchange.
		$testfile{$login}{"uid"} = "test-$login";
		$testfile{$login}{"Target-Address"} = "SMTP:$login\@test.com";
		$testfile{$login}{"objectClass"} = ["Top","person",
"Remote-Address"];
		$testfile{$login}{"mail"} = "$login\@test.com";
		$testfile{$login}{"MAPI-Recipient"} = "FALSE";
		$testfile{$login}{"textEncodedORaddress"} = "c=US\;a= \;p=Test
ORG\;o=TEST SITE\;s=$name\;";



-----Original Message-----
From: af...@t-... [mailto:af...@t-...]
Sent: Friday, November 10, 2000 5:11 AM
To: per...@li...
Subject: creating an entry on Exchange


I´m trying to add an enty to an Exchange 5.5 server via LDAP.
I´m doing the following and get a "Constraint error": What is missing?

$neuEintrag = $conn->newEntry();
$neuEintrag->setDN("cn=LisaM,cn=Recipients,ou=Einklang,o=Einklang.");
$neuEintrag->{objectclass} = ["Top", "person", "Remote-Address"];
$neuEintrag->{rdn} = ["lisam"];
$neueintrag->{cn} = ["lisa mona"];
$neueintrag->{sn} = ["mona"];
$neueintrag->{givenName} = ["lisa"];
$neuEintrag->{distinguishedname} =
["cn=LisaM,cn=Recipients,ou=FAG002,o=FAG001"];
$neuEintrag->{rfc822mailbox} = ["lisa\@test.com"];
$neuEintrag->{mail} = ["SMTP:lisa\@test.com"];
$neuEintrag->{uid} = ["lisam"];
$conn->add($neuEintrag);
$conn->printError() if $conn->getErrorCode();

maybe this is the wrong maillist, because I´m using PerLDAP 1.4.
If so, could someone please tell me what the differences are.

Thanks in advance

Re: creating an entry on Exchange

[Mark W. <mew...@un...>]

Yup, this is the wrong list. This the list for the Net::LDAP, the Pure
Perl  LDAP module (meaning no underlying C API is required). You got
confused becuase the website is called perl-ldap (we had the name first,
before Netsape marketing took the name for their module:).

Sorry, it's been too long since I've done anything with Netscape's module.
And I don't know anything about exchange.

Mark



Andreas Fecker wrote:

> I´m trying to add an enty to an Exchange 5.5 server via LDAP.
> I´m doing the following and get a "Constraint error": What is missing?
>
> $neuEintrag = $conn->newEntry();
> $neuEintrag->setDN("cn=LisaM,cn=Recipients,ou=Einklang,o=Einklang.");
> $neuEintrag->{objectclass} = ["Top", "person", "Remote-Address"];
> $neuEintrag->{rdn} = ["lisam"];
> $neueintrag->{cn} = ["lisa mona"];
> $neueintrag->{sn} = ["mona"];
> $neueintrag->{givenName} = ["lisa"];
> $neuEintrag->{distinguishedname} =
> ["cn=LisaM,cn=Recipients,ou=FAG002,o=FAG001"];
> $neuEintrag->{rfc822mailbox} = ["lisa\@test.com"];
> $neuEintrag->{mail} = ["SMTP:lisa\@test.com"];
> $neuEintrag->{uid} = ["lisam"];
> $conn->add($neuEintrag);
> $conn->printError() if $conn->getErrorCode();
>
> maybe this is the wrong maillist, because I´m using PerLDAP 1.4.
> If so, could someone please tell me what the differences are.
>
> Thanks in advance

creating an entry on Exchange

[<af...@t-...>]

I´m trying to add an enty to an Exchange 5.5 server via LDAP.
I´m doing the following and get a "Constraint error": What is missing?

$neuEintrag = $conn->newEntry();
$neuEintrag->setDN("cn=LisaM,cn=Recipients,ou=Einklang,o=Einklang.");
$neuEintrag->{objectclass} = ["Top", "person", "Remote-Address"];
$neuEintrag->{rdn} = ["lisam"];
$neueintrag->{cn} = ["lisa mona"];
$neueintrag->{sn} = ["mona"];
$neueintrag->{givenName} = ["lisa"];
$neuEintrag->{distinguishedname} =
["cn=LisaM,cn=Recipients,ou=FAG002,o=FAG001"];
$neuEintrag->{rfc822mailbox} = ["lisa\@test.com"];
$neuEintrag->{mail} = ["SMTP:lisa\@test.com"];
$neuEintrag->{uid} = ["lisam"];
$conn->add($neuEintrag);
$conn->printError() if $conn->getErrorCode();

maybe this is the wrong maillist, because I´m using PerLDAP 1.4.
If so, could someone please tell me what the differences are.

Thanks in advance

Re: What happens when I try to delete a non-existant attribute??

[Chris R. <chr...@me...>]

Tom Jordan <tj...@do...> wrote:
> 
> Hey folks,
> 
> I'd like to delete some attributes by feeding ldap->modify an arrayref,
> but due to my situation I've no guarantee that all of the attributes
> listed in arrayref will exist on the target object.
> 
> Does anyone know what the following code will return into $result if one
> or more of the attributes in $arrayref do not exist on the target object?
> 
> my $mesg = $ldap->modify($dn, delete => $arrayref);
> my $result = $mesg->code;
> 
> Alternately, can anyone think of a better way to go about this (or check
> first to see if the attributes exist?
> 
> Thanks much,
> 
> Tom Jordan
> University of Wisconsin Madison
> 

If you are connecting to your server using LDAPv3 (*not* LDAPv2) then you
could try using 'replace' instead of 'delete'.

The semantics of 'replace' changed rather dramatically between LDAPv2 and
LDAPv3, and in v3 (see RFC 2251 section 4.6) a replace with no values will
delete the entire attribute if it exists, and will be ignored if the
attribute does not exist.

Cheers,

Chris

creating an entry on Exchange

[<af...@t-...>]

I´m trying to add an enty to an Exchange 5.5 server via LDAP.
I´m doing the following and get a "Constraint error": What is missing?

$neuEintrag = $conn->newEntry();
$neuEintrag->setDN("cn=LisaM,cn=Recipients,ou=Einklang,o=Einklang.");
$neuEintrag->{objectclass} = ["Top", "person", "Remote-Address"];
$neuEintrag->{rdn} = ["lisam"];
$neueintrag->{cn} = ["lisa mona"];
$neueintrag->{sn} = ["mona"];
$neueintrag->{givenName} = ["lisa"];
$neuEintrag->{distinguishedname} =
["cn=LisaM,cn=Recipients,ou=FAG002,o=FAG001"];
$neuEintrag->{rfc822mailbox} = ["lisa\@test.com"];
$neuEintrag->{mail} = ["SMTP:lisa\@test.com"];
$neuEintrag->{uid} = ["lisam"];
$conn->add($neuEintrag);
$conn->printError() if $conn->getErrorCode();

maybe this is the wrong maillist, because I´m using PerLDAP 1.4.
If so, could someone please tell me what the differences are.

Thanks in advance

What happens when I try to delete a non-existant attribute??

[Tom J. <tj...@do...>]

Hey folks,

I'd like to delete some attributes by feeding ldap->modify an arrayref,
but due to my situation I've no guarantee that all of the attributes
listed in arrayref will exist on the target object.

Does anyone know what the following code will return into $result if one
or more of the attributes in $arrayref do not exist on the target object?

my $mesg = $ldap->modify($dn, delete => $arrayref);
my $result = $mesg->code;

Alternately, can anyone think of a better way to go about this (or check
first to see if the attributes exist?

Thanks much,

Tom Jordan
University of Wisconsin Madison

Re: Retrieve Image

[Mark W. <mew...@un...>]

$entry->get(..) returns an array context.

Thus you would need to do something like $image->[0] to get the actual
value.

If you're using the latest version of Net::LDAP, use
$entry->get_value(..) this will return the first value of the array if
called in a scalar context.

Mark

On Wed, 8 Nov 2000, Cary Z wrote:

> Hi, All,
> 
> I am trying to work out image processing in LDAP using Perl-Ldap. I used the
> following code to save the image into the database.
> ##################################
> open (in, "<clinton.jpg") or die "$@";
> $imagedata = <in>;
> close(in);
> $result = $ldap->modify($entry,  add => {'jpegphoto' => $imagedata});
> ##################################
> 
> After that, when I dump the content of the attributes, I found the jpegphoto
> attribute(which was not there before). So I assume it's ok.
> 
> Then I used this to retrieve it:
> ##################################
> $image = $entry->get('jpegphoto');
> print "Content-type: image/jpeg\n\n";
> print $image;
> ##################################
> 
> However I got this when the browser should only give me an image:
> 
> ARRAY(0X2BE0B8)
> 
> Could some one point me a way out. Thanks in advance.
> 
> - CZ -
>