EPrints Technical Mailing List Archive
See the EPrints wiki for instructions on how to join this mailing list and related information.
Message: #06859
< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First
[EP-tech] Document Security and Login
- To: "eprints-tech@ecs.soton.ac.uk" <eprints-tech@ecs.soton.ac.uk>
- Subject: [EP-tech] Document Security and Login
- From: Monica Wood <monica.wood@utas.edu.au>
- Date: Wed, 27 Sep 2017 07:17:04 +0000
Hi All,
We will be moving to SSO soon and as such I would like to change the default functionality of forcing a user to log in when trying to access a restricted document.
I would rather a user be given as error like ‘Cannot view this document’ or something similar and take them to the abstract page (or keep them at the abstract page if they started there) so they can then request the document.
The issue is, that we have repositories that harvest us, that link directly to the documents and not the abstract pages and this can cause confusion with people coming to us through these.
In the security.pl file I have tried setting it to DENY as a default, rather that have USER, but this hasn’t changed anything and under the permit subroutine in Document.pm both DENY and USER return 0, so it looks like there is no difference in these settings.
Does anyone have any idea on how I might be able to do this or where in the code base it determines if it sends the user to a log in page?
Cheers,
Monica Wood
|
- Prev by Date: Re: [EP-tech] SSL (HTTPS) only for an EPrints repository
- Next by Date: [EP-tech] Black overlay covers half of the webpage
- Previous by thread: [EP-tech] Periodically harvesting from multiple DSpace repositories into Dspace
- Next by thread: Re: [EP-tech] Document Security and Login
- Index(es):