Hi All,

  I would like to first apologize if this is documented or cover in another thread I searched here, the net, and the documentation and I think my question may be borderline out of scope for DNN.

  I have a DNN "test" portal set up, with pretty much all the "out of the box" settings being served via IIS.  I have static content also being served via IIS.  I want to display that static content in an IFrame in the portal to only authenticated users.  This work just fine but when I try to browse the content directly through IIS I can; that is a problem.  The folder permissions are set to allow NETWORK service to acces it and I believe that is the account that is serving the content to the un-authenticated John Q public user.  I have tried locating the content inside of the DNN structure to no avail.  What am I do wrong?  Is this even possible?  Thank you in advance for an help and or direction you can give me.

Sincerely,

~Charlie

Hi Chris,

  Thank you for your fast reply.  My static content will actually change from time to time based on a file update to a folder on the server; or that is my requirement anyway.  The intention is to have the content updated with a new content page of the same name so that that can be manually done without granting that person the Admin rights to the DNN portal.  I have been playing with the permissions and it seems that all authenticated users and IIS traffic to the DNN folder structure uses the ASP account; meaning there is no logical seperator at that level.

~Charlie

Hi Vitaly,

  Thank you for that piece, much appriciated; that is somehting I will try and push back with but the "static" content is really an HTML link structure to more than one page.  So it is not one flat page that can be copied in.  The marketing types have already stated that they would like it to have "multiple layers" as they put it in the Iframe content.  I think my answer is going to lying in playing with a separte site in IIS and protect that.  Then configure the IFrame to pass user parameters in the URL link.  That is the direction I am heading now.

~Charlie