I have deseperately been waiting for the relase of the source code for the new Active Directory Authentication Service Provider since DNN 4.6.0 was released.

The downloaded source code package of 4.6.0 didn't contain the source specifically for the Active Directory Authentication Service Provider. When I enquired about this I was given the response that the source code was currently going through the Release Tracker Process. So I've got a couple of questions, firstly how long does this process normally take? And secondly why is it that this process isn't completed prior to the release?

I'm not critisizing the project team regarding this, I just don't understand. I would have thought that if the implementation of the code is released then shouldn't the source code also be ready for release.

The reason for my desperation is due to the fact that I'm working on an intranet portal which has just hit the 1500 page mark with around 250 registered users. The number of users is due to jump by approximately 150 in the next couple of weeks when we roll the portal out to all areas of our company.

We have implemented Active Directory authentication across the portal but unfortunately one of the short comings of the current service provider is that it doesn't traverse Activie Directory to take into account users within nested AD groups.

I have 2 developers that are ready to begin looking at this issue as soon as they can get access to the source code, and once they have developed a solution we can provide it to the project team for incorporation within the source code of the project for the betterment of all.

If anyone can help me out with finding out what's happening with the source code for this project I would be very appreciative and so would anyone else that is facing the same issues related to nested AD groups.

Kind regards,

Adrian Scott-Day

Sorry Adrian, I only get email notifications on the AD provider forum.

This is my understanding of the process and it may be wrong but here goes. Under normal circumstances the provider would have had to go through the complete process before being released BUT if it hadn't been included with the release of 4.6.0 anyone using the AD provider in 4.5.5 and down would not have been able to upgrade until it passed through the Tracker. Because of that and because the AD Provider is essentially the same code just stripped from the core (I did a few tweaks) the install version was exempted from the full process this one time.  Any future versions will have to go through the Release tracker process before being released.

How long does the process take? That's a difficult question as an AD testbed setup isn't something that all of the assigned testers have. I'm trying to work with the core on a solution to that problem but it's slowing testing down.

Contact me offline (mhorton@telus.net) and I'll see what I can do about getting you the source.