On Thu, Jul 19, 2007 at 05:59:39PM -0400, Kyle Brentnell wrote: > Two possiblities come to mind right away. Others may have more elegant > solutions, that do not require DB or coding changes. > > 1) In the EPerson table set the "can_log_in" column to false for all > users(except the Administrator). This assumes anonymous users can not make > any changes to items (default Dspace behaviour). To allow access reset the > "can_log_in" flag to the original values. > > 2) Change the authenticateInternal method in the AuthenticationManager.java > class to always return "BAD_ARGS" or "NO_SUCH_USER", etc. to prevent users > from logging into Dspace. To allow access again, restore the original > authenticateInternal code (and compile and deploy of course).
These both seem reasonable, assuming you don't need to log in to be able to read content as well. Being able to flag various elements in the container hierarchy (from the entire site down to Items) as read-only has been on my wish list for some time, and DSpace provides no easy means for doing this readily. cheers, Jim -- James Rutherford | Hewlett-Packard Limited registered Office: Research Engineer | Cain Road, HP Labs | Bracknell, Bristol, UK | Berks +44 117 312 7066 | RG12 1HN. [EMAIL PROTECTED] | Registered No: 690597 England The contents of this message and any attachments to it are confidential and may be legally privileged. If you have received this message in error, you should delete it from your system immediately and advise the sender. To any recipient of this message within HP, unless otherwise stated you should consider this message and attachments as "HP CONFIDENTIAL". ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
