|
Just to follow-up on this issue, the fix was pretty
simple.
In the connection dictionary you have a couple of
options for auth type, None and Simple. I had just left it at the default
of None, so I assume it wasn't actually passing the auth credentials along to
the LDAP server, meaning I was only able to see information available to an
anonymous user, which obviously would not include a userPassword.
Changing the auth type to Simple seems to have
corrected the issue, at least in terms of reading.
I haven't tried writing back to LDAP yet, we'll see
how that goes.
Thanks to everyone who provided feedback on this
issue.
Cheers,
Mitch
----- Original Message -----
Sent: Friday, March 06, 2009 3:41
PM
Subject: LDAP and EOF
Hi,
I am trying to write a web based tool which reads
and writes to our organization's OpenLDAP directory containing customer
information.
I configured up a connection in entity modeler
and reverse engineered the schema which for the most part seemed to work
pretty well.
I can view a record for a customer given their CN
however the userPassword field from the core.schema is not
displayed.
If I have a look at how that attribute was
reverse engineered I see that it has been assigned an external type of octet
string which matches what is specified in the OpenLDAP schema. The java
type is NSData so I tried changing it to a String.
Unfortunately I still continue to get null when
trying to print the userPassword attribute, even though I can see that the
value is not null when I retrieve the same record using a little Perl script
which uses the same credentials to access the directory.
Has anyone encountered this particular issue
before, and is there a work around?
I am thinking that the issue is probably in the
way the schema was reverse engineered, but I'm not sure what to tweak to get
it to reveal that value.
Any comments or suggestions would be greatly
appreciated.
Thanks,
Mitch
|