The AuthentiX FAQ gives information on how to make AuthentiX the application work with IIS 6 sucessfully, but applying this fix, the site has not worked regardless of the change specified. Since the current version used is out of support, and the client is looking to upgrade to Forms Authentication, I had to make do with the problem. Over the weekend, I had to fix an issue where IIS 6.0, whilst running in IIS 5 Isolation Mode, suddenly (possibly due to a Windows Update) completely crashed IIS, so that it was unusable. IIS 6 kept coming up with the error “The path for the specified directory c... [More]

One of our clients use a 3rd party authentication tool called AuthentiX, which allows directory level authorisation and the use of multiple data sources to be used for IIS. Although ASP.NET has Forms Authentication, AuthentiX has been in use by the client for over 10 years and so co-existence with ASP was required to allow the retrieval of the username. Its usage is quite simple. If the code is executing on your page, they have been authenticated (or have they?) and given access to it. A code snippet of this COM component looks like this: protected void Page_Load(object sender, Event... [More]

I was continuing to help migrate some ASP code into .NET. My task this time was to bring the remaining part of the frameset (no, not using Master Pages yet), into .NET. So we have 3 parts: A Frameset page (ASP) Navigation (.NET) Content (.NET) Footer (.NET) But something odd was happening. When the first page request came in, 3 Global_asax.Session_Start events were generated. This caused major problems, as the frames all used the UserId , via the Session. BUT 3 Sessions were being created, and therefore not sharing any new data that went into it. The reason this was happeni... [More]