We use dspace-1.8 with custom code that I would like to simplify
Here is what we would like to achieve in terms of behavior:
* administrators authenticate via org.dspace.authenticate.CASAuthentication
* bitstreams in some collections are restricted by network IPs; we use
org.dspace.authenticate.IPAuthentication
* bitstreams in other collections are completely open access
* we do not ever want users with the ‘wrong’ IP address to be prompted for
login via an explicit authentication mechanism
* we do not anticipate ever restricting bitstreams such that users will
authenticate via an explicit mechanism
I looked around the code and noticed that the authentication manager offers
authenticateImplicit() and authenticate(). If item,collection,community pages
would trigger authenticateImplicit and admin pages authenticate, I believe
we’ll end up with the behaviour described above.
So the obvious questions here:
1. am I right ?
2. where do I need to change the code ? I envision a setting in dspace.cfg
(either global or collection/community specific) that could be used in a few
strategically place if statements
Monika
________________
Monika Mevenkamp
phone: 609-258-4161
Lewis Library,Washington Road and Ivy Lane, Princeton University, Princeton, NJ
08544
------------------------------------------------------------------------------
Flow-based real-time traffic analytics software. Cisco certified tool.
Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
Customize your own dashboards, set traffic alerts and generate reports.
Network behavioral analysis & security monitoring. All-in-one tool.
http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
