To deploy Tracker.Net using Windows Authentication, users must first be directed to a separate web application, which by default is named Tracker4Auth. You will need to set this up as a virtual directory in Internet Information Services (IIS). For example, the link might be something like this:
http://www.vbtrain.net/Tracker4Auth/Default.aspx
This application is in turn set up for Windows Authentication via these lines in its web.config file:
<authentication mode="Windows"/>
<authorization>
<deny users="?"/>
</authorization>
If users have not already been authenticated, they will be prompted with a dialog box like the one show below:
After authentication, they will be redirected to the Options screen if they have already been successfully added to the Tracker.Net database as explained in User Requirements below.
In order to use Windows Authentication, users need to be preloaded into Tracker.Net using either the Student Import Utility or directly into the Tracker_Students table in the database.
The User Name needs to be set to the name of the user (for example User.Identity.Name or Request.ServerVariables("LOGON_USER")). This ends up being domain name/user as in Jeff-PC\Jeff.
The password needs to be set to the user's Security Identifier (SID). In .NET code this is User.Identity.Value. An example value is S-1-5-21-2264705100-1831356049-1397210148-1001.
It is important to set the ExitURL on the Global Settings screen to be a value outside of Tracker.Net since otherwise users exiting the system will be in an endless loop of being redirected to the Options screen. Custom Messages are not supported under Windows Authentication although Custom Organizations are supported. Other values such as the ability to email user names and passwords are not application to Windows Authentication as well.