Posted by Schwab,Wilhelm K on Feb 16, 2011; 2:50pm
URL: https://forum.world.st/Pharo-LDAP-tp3308841p3308970.html

I have used LDAPlayer with good results.  There are small problems on Pharo - a DNU over #and:and: IIRC.  As the self-appointed silent failure pedant, I would like to suggest a change to your code.  Please try/consider (untested code):

attrAt: aKey ifNone:ifNone
     | selected |
     selected := attrs at:aKey ifPresent:[ :value | aKey asByteArray ] ifAbsent: [ ^ifNone value ].
     ^ selected first asString.

That way, one can know whether the item was missing, treating that condition as an error or ignoring it as appears to work in your case.  My images are littered with #asByteArray methods, which complicates spotting what that might be doing.  The change above (hopefully??) preserves the original behavior when the attribute is present; at least that was my goal.


________________________________________
From: [hidden email] [[hidden email]] On Behalf Of Olivier Auverlot [[hidden email]]
Sent: Wednesday, February 16, 2011 8:41 AM
To: [hidden email]
Subject: [Pharo-project] Pharo & LDAP

Hi,

For a project of REST services with Pharo and Seaside, I need to send
requests to an LDAP server. I found a project named LDAPlayer on
squeaksource.

Now, I can create a connection and do a request to the LDAP server.

But... my problem is to read an attribute in the result. In the
LDAPSearchResultEntry object, the method to get a value is :

attrAt: aKey
     | selected |
     selected := attrs at: (aKey asByteArray) ifAbsent: [ ^ nil ].
     ^ selected first asString.

The problem seems to be on the third line with the use of the
asByteArray method. Why used this method ?

For my tests, I remplaced it with :

selected := attrs at: aKey ifAbsent: [ ^ nil ].

And now, it's ok but I don't know if my modification could introduce
others problems.

What do you think about that ? Someone has used LDAPlayer with Pharo ?

Best regards

Olivier ;-)

www.auverlot.fr