Hi Yongming, Have you checked to make sure your DSpace 5 configurations have been updated per the configuration changes noted in the DSpace 6 upgrade docs? https://wiki.duraspace.org/display/DSDOC6x/Upgrading+DSpace
In other words, I believe the IP authentication configurations changed names slightly between DSpace 5 and DSpace 6. See also, https://wiki.duraspace.org/display/DSDOC6x/Authentication+Plugins#AuthenticationPlugins-IPAuthentication If you have updated all your configurations, then it's likely this *is* a bug in DSpace 6. There was no change in behavior expected between DSpace 5 and 6. So, in that scenario, I'd encourage you to submit this bug to our ticketing system at https://jira.duraspace.org/projects/DS/ If you do not yet have an account, you can request one through [email protected] If you or your team have time to dig into the code to look for the bug, we also welcome code contributions. DSpace is definitely a community effort, so we appreciate any bug fixes that community members are also able to provide. https://wiki.duraspace.org/display/DSPACE/Code+Contribution+Guidelines Tim On Thu, Jan 19, 2017 at 9:37 AM Wang, Yongming <[email protected]> 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 <(609)%20771-3337> > email: [email protected] > > -- > 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. > -- Tim Donohue Technical Lead for DSpace & DSpaceDirect DuraSpace.org | DSpace.org | DSpaceDirect.org -- 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.
