On Wed, Jun 27, 2012 at 10:47 PM, Shixing Wen <[email protected]> wrote: > Hi helix84, > > Thanks for your instructions on how to set up IP authentication. Indeed, we > just need to restrict access to bitstreams, not metadata. However, we have > tried many times but it is still not working. > > Does a user need to be an e-person before s/he can access a collection > restricted by IP ranges? That would be cumbersome. That would mean everyone > on campus has to go through the creation of an account process in DSpace. I > thought an IP authentication would grant any users with access to the > restricted collection when s/he is using an IP address that is within the IP > ranges we've added to the config file. > > By the way, we use DSpace jspui v. 1.6.0 > > Any advice? > > Shixing
Please, always CC dspace-tech. I just tested it again and it does work. You do not have to be logged in, I was just telling you where you can check your current group membership for testing purposes. I suspect you may be running into another problem, which is explained here: https://wiki.duraspace.org/display/DSPACE/TechnicalFaq#TechnicalFaq-Ichangedaccessrestrictionsonacollections%2Cbutrestrictionsdidn'tchangeonitsitems Read it carefully. Make sure you have the correct group READ authorization set on bistreams, not on collection! For existing items, you have to set it either manually or via the wildcard policy admin tool. Regards, ~~helix84 ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
