Using the login.specialgroup, along with removing default read access to the collections, does restrict access to collections listed on the home page. However, anonymous access is still available to items made available by Discovery. That is, in the 'Recently Added' section, or via search, or the browse lists.
Removing anonymous read access from items' bitstreams and replacing it with read access for the authenticated special group does work, but I'm going to have to repeat this process every time a new item is added. Also, the wildcard policy admin tool seems to time out when used on multiple collections, or even large collections (> ~1000), in which case the items are not modified. I suppose I could modify the UI to remove the ability to use discovery, etc., but that rather defeats the purpose of using DSpace. Is there a better approach? My goal is to have all items available to logged-in users, but nothing available to anonymous users. DSpace version: 6.3 XMLUI Mirage2 theme On Wed, 27 Jan 2021 at 15:28, Sean Carte <[email protected]> wrote: > Thanks, José! > > On Wed, 27 Jan 2021 at 14:54, José Geraldo <[email protected]> wrote: > >> Hi, >> >> You can use the "login.specialgroup" and change the READ policy for this >> group. >> >> >> https://wiki.lyrasis.org/display/DSDOC5x/Authentication+Plugins#AuthenticationPlugins-ConfiguringAuthenticationbyPassword >> >> Em qua., 27 de jan. de 2021 às 05:30, Sean Carte <[email protected]> >> escreveu: >> >>> Is there a way to restrict access to logged-in users only, so that >>> anonymous access to collections requires a log-in? >>> >>> I understand that I can simply remove the anonymous READ authorization >>> for a collection, but then I would need to create a READ authorization for >>> a particular group, and there isn't a 'logged-in users' group. >>> >>> I'm sure I must be missing something very obvious here, please could >>> someone enlighten me. >>> >>> DSpace version: 6.3 >>> SCM revision: 813800ce1736ec503fdcfbee4d86de836788f87c >>> SCM branch: UNKNOWN >>> OS: Linux(amd64) version 4.15.0-130-generic >>> Applications: >>> Discovery: enabled. >>> JRE: Private Build version 1.8.0_275 >>> Ant version: Apache Ant(TM) version 1.10.5 compiled on March 28 2019 >>> Maven version: 3.3.9 >>> >>> -- >>> All messages to this mailing list should adhere to the DuraSpace Code of >>> Conduct: https://duraspace.org/about/policies/code-of-conduct/ >>> --- >>> 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 view this discussion on the web visit >>> https://groups.google.com/d/msgid/dspace-tech/CA%2BxAuhNVyzuQTjSaQCEmVq2DS7PTh8Pf_XeoYPMa-cOUvGPybA%40mail.gmail.com >>> <https://groups.google.com/d/msgid/dspace-tech/CA%2BxAuhNVyzuQTjSaQCEmVq2DS7PTh8Pf_XeoYPMa-cOUvGPybA%40mail.gmail.com?utm_medium=email&utm_source=footer> >>> . >>> >> >> >> -- >> At.te, >> >> José Geraldo >> >> -- All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/ --- 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 view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/CA%2BxAuhOjVZegc7NWRkk8gCLL1S12TJ8huvQYykSBE6r0CJySJg%40mail.gmail.com.
