Hi team, We are using *dspace **7.6.1(dspace-backend as our code and dspace-ui as docker image)* and deployed on gcp kubernetes. I have so many communities and inside that so many nested communities and collections, all are open to read by *anonymous users*, now we want to revoke read access from *anonymous users* for all existings and newly communities and collections.
I have found some suggestions from google that I would have to add below properties at *dspace.cfg* file. *# Disable anonymous read access to collectionswebui.anonymous.read.collection = false# Disable anonymous read access to communitieswebui.anonymous.read.community = false# Disable anonymous read access to itemswebui.anonymous.read.item = false* I deploy with above properties but still not working for me. Please help me on same. Thanks, -- All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx --- You received this message because you are subscribed to the Google Groups "DSpace Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/dspace-community/f6cc3097-19e9-4f59-82a8-5236bde4f8d3n%40googlegroups.com.
