The next release of the Active Directory provider is now available. This release contains only bug fixes that fix a couple of major issues that recently came to light.

The next release of the Active Directory provider is now available. This release is mainly bug fixes but does have one new, and major, capability. Thanks to Ash Prasad the provider now supports LDAP. 

The Active Directory provider has moved from RC to Release

It's been a long time since I've blogged here on the DotNetNuke site. So long that I had to look to see when my last one was (7/30/2009). At that time it was to announce the release of the 05.00.02 version of the provider. So, almost two years since I've blogged and just that long since a release of the provider. I could say that the provider is just that good that there's been no need for a release but, as I'm sure the users of the provider can attest, that's just not the case.  Why hasn't anything been happening with the provider in all that time? Well a number of things. The primary reason is that my life has gotten extremely busy in the last two years. At the time of the last release I was spending all my free time prepping for my black-belt test in Taekwondo and once I passed the test (November of 2009) I started teaching the beginner classes at the dojang three nights a week (prior to that I was assisting the regular instructors in their classes). Add in family commitments and working on the provider just kept getting pushed to the back-burner. Every month I'd plan to spend at least an hour a night on the provider getting bug fixes done and enhancements added but it just wasn't happening. Now, that's not to say that the code sat there dormant without being looked at all this time. I would open the solution now and then and fix a bug or look at a problem but it never got down to the point where I was ready for a release....

Version 01.00.06 of the Active Directory provider has been officially released. Please note that this version is only for the DNN 4 stream of DotNetNuke (4.6.2 and up).

Primarily this release is to make sure that both streams of the provider (DNN 4 and DNN 5) are comparible. There were some breaking changes in DNN 5 that required code changes on the automatic registration and login of users.

A complete list of changes can be found in Gemini.

Support for the provider can be found the the Authentication Providers forum.

The provider source and install package can be found on the Codeplex Active Directory project's download page

Version 05.00.02 of the Active Directory provider has been officially released. Please note that this version requires the upcoming DotNetNuke 5.1.0 as the minimum version.

Primarily this release is to make sure that both streams of the provider (DNN 4 and DNN 5) are comparible. There were some breaking changes in DNN 5 that required code changes on the automatic registration and login of users.

A complete list of changes can be found in Gemini.

Support for the provider can be found the the Authentication Providers forum.

The provider source and install package can be found on the Codeplex Active Directory project's download page

 

 

 

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.

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...

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

 

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

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).

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

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

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...

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...