Summary: | Show certain links just for registered users | ||
---|---|---|---|
Product: | Koha | Reporter: | Hugo Agud <hagud> |
Component: | OPAC | Assignee: | Bugs List <koha-bugs> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | katrin.fischer, tomascohen |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: |
Description
Hugo Agud
2018-03-05 11:56:44 UTC
Hi Hugo,
I think just controlling the visibility is not a good way of protecting restricted resources. Links can be shared or keep working, if your account has been blocked or deleted. What you need to implement, I think, is a protection of the resource itself, that Koha can't provide unless it's stored within Koha itself.
> These conditions are the same than ILL request.
Can you explain?
(In reply to Katrin Fischer from comment #1) > Hi Hugo, > > I think just controlling the visibility is not a good way of protecting > restricted resources. Links can be shared or keep working, if your account > has been blocked or deleted. What you need to implement, I think, is a > protection of the resource itself, that Koha can't provide unless it's > stored within Koha itself. We could add that functionality to Koha uploads. Some sites work with the referer as a way to validate the request, so hiding the links could help. But that'd be certainly a separate featurre: optionally removing 856 fields based on some regexp and config. Another thought: woudn't it be better to show the link and ask for login before access? That way users can discover the existence of the resources, otherwise they might not even notice. Hi Katrin.. yes it is a good issue!! thanks! |