I have a MVC .net website that i deploy using Octopus Deploy to a Windows 2008 server
Every time I Deploy a release the Windows Authentication is set back to Disabled
The test version of the site is also on a different Windows 2008 server but this does not disable the setting.
My gut reaction might be that it IIS thats doing this rather than Octopus but don't want to rule that out at this stage.
We also had this problem using Octopus Deploy. Deploying to the testing environment went OK, with IIS keeping Windows Authentication = enabled, but when deploying to the dev environment then Windows Authentication was switched to disabled.
The solution for us was to edit the applicationHost.config file in the webserver (under C:\Windows\System32\inetsrv\config) and add a location-section for the site at the end of the file (but before </configuration>
) like this:
<location path="MyWebSite">
<system.webServer>
<security>
<authentication>
<windowsAuthentication enabled="true" />
</authentication>
</security>
</system.webServer>
</location>
After this, the Windows Authentication setting was kept at enabled after deploy.