Mike Horton

Active Directory Provider 01.00.04 Released

mike.horton@dotnetnuke.com — Wed, 27 Aug 2008 07:00:00 GMT

I'm happy to announce that the 01.00.04 version of the Active Directory Provider has passed through the DotNetNuke Release Tracker. While there are only about a dozen bug fixes in the release and no new features a couple of the bug fixes are significant performance-wise.

More...

01.00.03 Active Directory Provider Released

mike.horton@dotnetnuke.com — Thu, 27 Mar 2008 07:00:00 GMT

I'm pleased to announce that the 01.00.03 version of the Active Directory Provider has completed the DNN Release Tracker process and has been released. You can download the provider and the document from the Authentication Provider project page (http://www.dotnetnuke.com/Products/Development/Forge/Authentication/Downloads/tabid/852/Default.aspx).

Changes/Fixes for this release:
ACD-3084 Authentication Configuration.ResetConfig()-does not clear Provider from cache
ACD-4641 AD Module Does Not Detect Membership of Nested Groups
ACD-5563 Passed Parameters Lost When WindowsSignin.aspx is called
ACD-6416 Displayname gets always set, even if a rule is setup
ACD-6451 AD Provider Cannot Be Disabled
ACD-6452 WindowSignin Processing AD Credentials
ACD-6493 "Mixed-Mode" logins
ACD-6901 App Not Initialized Before Active Directory Call
ACD-7038 No Warning that autologin does not work under IIS7/Integrated Pipeline

OpenID and LiveID Source Released

mike.horton@dotnetnuke.com — Sun, 27 Jan 2008 07:00:00 GMT

I'm pleased to announce that the source code for the LiveID and OpenID providers has been released.

More...

Active Directory 01.00.02 Provider Status Update

mike.horton@dotnetnuke.com — Wed, 16 Jan 2008 07:00:00 GMT

More...

Active Directory Provider and DNN 4.8.0 Problems.

mike.horton@dotnetnuke.com — Fri, 28 Dec 2007 00:10:42 GMT

The short summary is that you shouldn't upgrade to DNN 4.8.0 if you need to use the Active Directory provider.More...

Active Directory Provider 01.00.01 In Release Tracker And New Documentation

mike.horton@dotnetnuke.com — Tue, 11 Dec 2007 18:26:20 GMT

Just a short note to let everyone know that I submitted a new version of the provider to the Release Tracker yesterday (http://www.dotnetnuke.com/Products/Development/ProjectReleaseTracking/tabid/997/Default.aspx). I also got the documentation done for the 01.00.00 version of the provider. It can be found in the Project's Download Area under Other Files (http://www.dotnetnuke.com/Products/Development/Projects/ProviderAuthentication/tabid/840/Default.aspx). More...

Active Directory Provider Available For Download

mike.horton@dotnetnuke.com — Tue, 20 Nov 2007 18:29:34 GMT

For those of you patiently awaiting for the source code your wait is over.More...

DNN 4.6.0 and the Active Directory Provider

mike.horton@dotnetnuke.com — Wed, 17 Oct 2007 03:51:31 GMT

There are a few considerations or changes when using the newly separated from the core AD Provider.More...

Active Directory Provider Problems

mike.horton@dotnetnuke.com — Thu, 14 Jun 2007 16:05:27 GMT

I just returned from a three day camping trip with my son's grade six class in the foothills of the Canadian Rockies to a mailbox full of people having problems with Active Directory. It was quite a shock to the system as it's been a long time since I was totally without internet access for more than a day.

It looks like a change somewhere in the core has broken AD websites that use full authentication (the authentication line is uncommented in the web.config) but mixed-mode authentication still works (users log into the DNN site using DOMAIN\Username and their AD password or use a link to the windowssignin.ascx) in single portal installs (multiple parent/child portals is another matter). I've been able to recreate it on a test site but then was able to fix it by deleting the AD user from the DNN site and then visiting again. Once the account was recreated everything worked fine. However, this is not an ideal solution (deleting all current users) on a portal that has thousands of users.

I've got today and tomorrow to catch up on things here at work and then I'm on holidays and will be able to dedicate my full attention to the problem rather than the 15 minutes here and 30 minutes there that I've been able to the last couple of weeks but wanted everyone to know that we're aware of the problem and are not ignoring it.

Active Directory Provider News

mike.horton@dotnetnuke.com — Wed, 25 Apr 2007 04:00:00 GMT

Hello everyone.

After many discussions with Joe Brinkman and Scott Willhite about the Active Directory provider I decided it was time to "put up or shut up" and applied to be the Project Lead. Imagine my surprise when the answer was "Yes".

Seeing as this is my first blog here I guess I should tell you a little about myself. I've worked with computers doing programming on a personal level since the very early 80's. On a professional level I've worked in an IT position at a Technical College in Edmonton, Alberta, Canada for the past 10 or so years where I do a bit of everything (computer repair, server administration, programming, etc). I discovered DotNetNuke back in it's early days (I believe it was version 1.0.6) and quickly became a convert. When I'm not working on the computer I'm either watching some form of motorsports, at TaeKwonDo with my eleven year old son, or spending time with my wife and two teenage daughters.

But enough about me when what you really want to know about the AD provider. If you check the project page you'll notice that Charles Nurse is now the Core Team Sponsor. While some might think it's a mistake to put two Crazy Canucks together on a project I don't think so. Charles is very familiar with how the Active Directory provider is tied in with the core code and is going to be a great help in going forward.

So what direction is the Active Directory provider headed? What Charles and I would like to do is separate the AD code from the core and make it an actual provider. This serves, at minimum, two purposes. It can become a separate project that isn't reliant on core code releases with it's own release schedule much like you see with the other DotNetNuke projects. It will also make it easier to add other versions of authentication making the provider much more rugged.

Over the next few days I'm going to get far more familiar with the AD code and start looking at ways to meet our initial goal of separating the code from the core. Also once I'm a bit more settled into the Project Lead position I will most likely be looking for project team members so if you're interested be prepared.

Thanks
Mike Horton