On Fri, Mar 12, 2010 at 11:38:35AM -0600, Dorothea Salo wrote:
> What we can't do that I would very much like us to:
> 
> - automagically populate the eperson directory based on LDAP login
> results and lookups (you logged in? congrats, you're an eperson! an
> admin looked you up? congrats, you're an eperson!)

I thought it already did that.  (webui.ldap.autoregister) Yes, when
enabled it will set the EPerson's email, given name, surname, and
phone from the LDAP response if they were present.  Mmmm, well, it
does when you log in, but maybe not if the admin created your record
-- that would be helpful.

But I also think that's wrong-way-round.  Instead, DSpace should just
remember whence came the original authentication which allowed the
creation of an EPerson.  Local: store other user data locally.  LDAP:
go out to the directory whenever an EPerson attribute is wanted (with
a cache, perhaps).

All we need to know, to attribute a session to an EPerson, is that
authentication of a certain net-id succeeded.  All we need to know, to
fulfil a subscription, is how to get a given EPerson's current email
address.  I think that anything about an EPerson which DSpace doesn't
have to store, DSpace should not store.

[decorate sessions with groups based on various criteria that the
directory should provide]

A fairly general way to map LDAP_group->DSpace_group at logon would
help, if the data are in the directory.

> Obviously this is not entirely DSpace's fault; our LDAP can't actually
> give us a lot of this information.

I hear you.  We face similar problems here. :-{ We complain for a
decade and things finally move a little.

-- 
Mark H. Wood, Lead System Programmer   [email protected]
Friends don't let friends publish revisable-form documents.

Attachment: pgpVR2A0wnBTs.pgp
Description: PGP signature

------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech

Reply via email to