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 Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/dspace-tech/fc961e54-ab3e-4a4f-8d3e-b91df11c2426n%40googlegroups.com.
