This is a work in progress on how to setup Windows Authentication by making the default namespace public and the other namespace private. -- AstralisLux

Criteria

• Using version # 1.8.0.1696 but all versions probably follow the same procedure
• The default namespace is public
• Using Windows Server 2003, IIS 6.0
• Using FileSystem storage, not MSSQL Server
• Wiki is on the internet
• Have a secondary namespace already created
• Create a user in IIS Computer Management console and set a password

About Windows Authentication

• There are tons of docs on the web about getting integrated security set up with IIS and ASP.NET. FlexWiki isn't really doing anything here - all the security gunk happens before FlexWiki gets involved. Users must be Windows users that exist or are accessible (in the case of domain accounts) on the web server machine...that's what "integrated" security means. -- CraigAndera
• You are in fact using Windows authentication. That should mean that users who visit your site must be authenticated from a Windows perspective. However, you aren"t yet using impersonation -- that's what causes the ASP.NET app (in this case FlexWiki) to use the identify of the visiting user in operations such as accessing the file system. -- DavidOrnstein

Initial steps

1. Be sure you match all the criteria above.
2. In your IIS, right-click on the folder which is mapped to your wikibases folder.
3. Click on properties. Click on Directory Security tab.
4. Click Edit in the Anon Access area.
5. In the Authentication Methods window, select the Integrated Windows Authentication check box. (This sets permission for only the folder you selected in the first step.)
6. Click off anonymous access (if checked).
7. You also need to modify permission for the filesystem folder (not the IIS directory). You'd typically do that using Windows Explorer. Right click this folder, pick "Security and Sharing" and under Security grant read and/or write permissions to users you'd like to be able to read or write to that namespace. Note that these users must be Windows users that exist or are accessible (in the case of domain accounts) on the web server machine. That's what "integrated" security means. (You may need to remove some of the machine users.)
8. For this to work, the following must appear in your web.config file:

 <authentication mode="Windows" />
 <identity impersonate="true" />

Errors

After I thought I had this set up correctly, once I created my first topic I discovered that the system would not let me view the page and redirected to its edit page anytime I clicked the topic name. Once I discover why this is doing this and if there's a fix I'll post it. -- AstralisLux