Dear Sir, I'm also facing the same problem, did you get the solution. please help me.
Buddhin On Thursday, January 19, 2017 at 9:07:52 PM UTC+5:30, Wang, Yongming wrote: > > Dear all, > > We've recently upgraded from 5.1 to 6.0. We encountered a problem for our > ip range restriction feature. > > In 5.1, we set READ restriction by ip range to all bitstream of certain > collection. If an anonymous user is in the ip range, this user doesn't need > to login to open the bitstream. But in 6.0, even the anonymous user is > indeed in the ip range, this user still needs to login to open the > bitstream. The problem is that we have disabled the new user registration > feature. So now NONE of the anonymous users within the ip range can open > this collection's bitstreams. > > I've tested our new configuration of ip range restriction. It seems to be > correct because I logged in with my testing account in the ip range and I > can open the bitstream and also my profile has listed as a member of this > restriction group. > > Question: > > Is this change of behavior intended for 6.0? If so, I guess we have to > enable the new user registration. > > Or it's just a bug? > > > Thanks in advance for any tip and help! > > > > Yongming > > -- > Yongming Wang > Systems Librarian/Associate Professor > The College of New Jersey > tel: 609-771-3337 > email: [email protected] <javascript:> > -- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
