Hello Everyone:
I wanted to open this up to a general audience. I'm not sure of whether or not what I'm running into is considered to be a bug, or not.
Without installing anything, you can use the <code>Secure</code> folder type to create a "secure" folder in which you can assign user/role permission. This allows you to ensure that only intended people can access the file(s) in the respective folder.
This seems to work well. Now...
We've installed and attempted to use two different folder providers since then. First, the built-in Azure Storage Connector and the Evotiva DnnGlobalStorage folder provider. In both instances, if any permission is applied to the folder(s) in question, the URL is indeed obscured by using LinkClick, but the resulting URL can still be fully accessible via Incognito mode without being logged in.
This sounds like a bug to me. Can anyone verify whether or not I'm on the correct path... It doesn't make sense to be able to assign settings, but they don't really apply to anything exception DNN admin/edit views.
These Forums are for the discussion of the open source CMS DNN platform and ecosystem.
For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:
Awesome! Simply post in the forums using the link below and we'll get you started.