Hello,
The institution for which I work is planning to deploy DSpace in the near
future, and I am hitting a wall regarding authentication issues.
I am attempting to use the Embargo feature on a subset of items within a
collection. I am able to successfully set the embargo on the desired items,
but I am having difficulty allowing users that are IPAuthenticated to access
the bitstreams. Is this expected behavior, or am I likely doing something
wrong?
I am using DefaultEmbargoSetter to set the embargo on the items.
I have added org.dspace.authenticate.IPAuthentication to the top of the
authentication stack in dspace.cfg.
I have added authentication.ip.MY_UNIVERITY = [ip ranges] to dspace.cfg.
I have added a DEFAULT_BITSTREAM_READ policy for the group MY_UNIVERSITY.
I am not seeing any configuration error messages in dspace.log.
When I try to view an embargoed bitstream from within a defined ip range for
MY_UNIVERSITY, I am taken to the login screen with the message "The file you
are attempting to access is a restricted file and requires credentials to
view. Please login below to access the file."
Any advice or information on what I may be doing wrong is greatly
appreciated.
Thank you,
Dave
------------------------------------------------------------------------------
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-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
