Hi, after following the directions in the codeplex documentation section I can not get AD authentication working using the latest build of DNN. I've has AD authentication running for years using previous versions, but this is the first server running Win2k8 R2/SQL 2008 and v7.1

The event viewer shows this error after trying to manually login using Windows Authentication..

Can anyone shed any light on this?

Any help would be appreciated
Thanks.. Mark

AssemblyVersion: 7.1.0

PortalID: 0

PortalName: My Website

UserID: -1

UserName:

ActiveTabID: 57

ActiveTabName: Home

RawURL: /Login?returnurl=%2f

AbsoluteURL: /Default.aspx

AbsoluteURLReferrer: http://akowww/Login?returnurl=%2f

UserAgent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/5.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; .NET4.0C; .NET4.0E)

DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke

ExceptionGUID: 1ccaf0bd-5065-48e2-a0b3-5ccfd8f0d927

InnerException: This Membership Provider has not been configured to support password retrieval.

FileName:

FileLineNumber: 0

FileColumnNumber: 0

Method: System.Web.Security.SqlMembershipProvider.GetPassword

StackTrace:

Message: DotNetNuke.Services.Exceptions.PageLoadException: This Membership Provider has not been configured to support password retrieval. ---> System.NotSupportedException: This Membership Provider has not been configured to support password retrieval. at System.Web.Security.SqlMembershipProvider.GetPassword(String username, String passwordAnswer) at DotNetNuke.Authentication.ActiveDirectory.AuthenticationController.AuthenticateUser(UserInfo objUser, ADUserInfo objAuthUser, UserLoginStatus& loginStatus, String ipAddress) at DotNetNuke.Authentication.ActiveDirectory.AuthenticationController.ManualLogon(String userName, String strPassword, UserLoginStatus& loginStatus, String ipAddress) at DotNetNuke.Authentication.ActiveDirectory.Login.cmdLogin_Click(Object sender, EventArgs e) at System.Web.UI.WebControls.LinkButton.RaisePostBackEvent(String eventArgument) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) --- End of inner exception stack trace ---

Source:

Server Name: XXXXXX

DNN 7.1 + Hashed passwords + AD provider = No workie....

the first problem you will run into is that error message "This Membership Provider has not been configured to support password retrieval." error. To fix that you have to revert back to encrypted passwords.

AFTER changing back to encrypted passwords the second problem you will run into is the password history table wants to log those login attempts when AD fires so to get around that "temporarily" I had to allow null inserts into that table. It's not the optimal solution but it will work until we can find a better way. Once you allow nulls on that table it will start working but it's a hack to get you by until the solution is permanently resolved.

I'm not near an install at the moment so I can't check what I've got the password encryption set at (pretty sure it's the default whatever that is). However, I think I know what's happening. Because the provider stores randomly generated passwords in the DNN database the code has to pull down what is currently stored in the database to complete the login.

Has anyone logged this in Codeplex (http://dnnauthad.codeplex.com) so that I know to look at it?