Hi...
Here at Cornell University, we are trying to figure out the best way to handle
authentication in DSpace.
Right now I am using DSpace's native authentication system for the majority of
collections, but I have been asked to limit access on some collections to the
Cornell Community. In those cases, I have been forced to use a locally
developed software package called CUWebAuth (which is Kerberos based) because I
am not allowed by our Security people to use LDAP except through the CUWEbAuth
application. CUWebAuth runs on Apache, uses permits and is directory-based, so
I can lock items down by defining them in an Apache Config file (each item
declared separately using "<Location /handle/xxx/xxx>"). You can imagine this
is pretty cumbersome.
I am curious if anyone in the DSpace Community has had a similar situation of
limiting access to collections and/or items to a large group of individuals and
how they may have done this.
Thank you.
George Kozak
Digital Library Specialist
Division of Library Information Technologies (DLIT)
501 Olin Library
Cornell University
Ithaca, NY 14853
607-255-8924
------------------------------------------------------------------------------
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
