We have been attempting to add Active Directory authentication to our site to provide access on our public site to an intranet area for our users inside the domain.
Originally set up on DNN 5.1.2 (AD 5.0.2) we did successfully get it working (with some exceptions, like older AD accounts had trouble logging in for some reason and auto-login seemed inconsistent and browser specific, but functional)
The problem was the site's inability to be indexed by Google, fetch as googlebot in the webmaster's tools revealed a 302 redirect error and the site has been dropped...
Searches revealed a known issue with the version, and the update advertised a fix for the problem.
So, we've updated to DNN 6.1.3 (latest version, afaik) and installed the AD provider 5.0.3. We're getting green lights down the board for our authentication settings and domain users are able to log in as expected (even the auto-login seems more reliable).
The problem is that fetch as googlebot is _still_ returning a 302 redirect...
I have looked through all the forums and the support material, but can find no hints about what the problem is. As this is an issue that was mentioned in the update notes for the provider as something that is fixed, I expect that it is something in my configuration, but have had no luck figuring it out.
I see an "Allowed Search Bots" field in the settings and as this looks very promising, I've played with various entries here (Googlebot, google bot, Google...) but no effect, and very few leads found through searches for appropriate entries for this setting.
Anyone know what I might be missing? Would greatly appreciate any advice...
thanks in advance,
Forest and domain functional level - 2003 Windows Server
2005 SQL Server Standard
Windows Server 2003 (SP 2)