Wes Tatters wrote:
I would definitely suggest this is something you need to talk to your site admins about - you should never go playing with permissions in any server environment that you dont fully understand.
West
Thanks Wes for your advice,
It's not that simple though. Setting up the DNN site has been sort of a guerilla war from the start. My boss supports me, but the IT management think that I should use the system they sanction within the organization, that is EpiServer and IBM Social. I believe that DNN is a better solution, and I am setting it up to proof that I am right. Sometimes I fell that the company is allergic and suspicious to anything that doesn't cost a million bucks to implement.
Anyway, I tested my own suggestion to look into ASP Impersonation.
I did the following:
- In IIS Manager, click on Authentication.
- For ASP.NET Impersonation, change to "enabled"
- Choose "edit"
- Then select a domain user that have appropriate access
- Press OK
After I had done this, I restarted IIS. First nervous thing to check was if DNN started as it should, and yes it does.
Then I went to Admin -> File Management and "Manage folder types" and added a UNC folder through the "Evotiva-WindowsUNCFolderProvider".
Under "ASP.NET Identity" it actually shows the impersonating user as DOMAIN\USERNAME and when I add the UNC folder and choose "test connection" it works! It says "The Windows UNC Connection is valid" Yippie!
So I am really happy and can continue to configure DnnSharp Boost search and show everybody why the DNN solution is the best of breed!
Thanks for the help Wes, to help me find this great module from Evotiva.