Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationerrors with AD provider after upgrade to DNN 6.0errors with AD provider after upgrade to DNN 6.0
Previous
 
Next
New Post
8/11/2011 3:30 PM
 
I think I might see a cause to the problem. You say the application pool is running in integrated mode. The 5.0.2 version of the provider doesn't support integrated mode. The 5.0.3 version does support integrated if the two commands that are posted in the readme are run. I'd have to check my dev system @ home as far as using the 4.0 framework. The software was coded under the 3.5 framework and I've seen funky things happen under the 4.0 framework with other software.
 
New Post
8/17/2011 3:52 PM
 
I am also getting this error on the login page. My app pool is running in classic. The AD provider is working great except for this login page error. I'm using DNN 6.0, and .NET 4.

Im thinking about just adding a redirect on the login page to the http://myweb.scentsy.local/DesktopModules/AuthenticationServices/ActiveDirectory/WindowsSignin.aspx page. That seems like a hack though, I'd rather just have this provider work.
 
New Post
8/26/2011 5:56 PM
 
Hi, just thought I'm mention that we're getting the same error with DNN6 (DN6.0.1). We're using classic (and .NET3.5). I've never had this error in DNN5.x series, so something must have changed in 6 that is causing this issue with oldPassword. Am still investigating it myself, but it definitely is happening to more than just the one person.
thks
 
New Post
8/29/2011 3:04 PM
 
i was able to solve this problem by making the following change within the code (we actually converted this AD provider to an LDAP provider a while back, so our code does not match and many places but I'm assuming this line exists in some fashion in the AD code as well (it is actually in multiple places in our LDAP version).

Changed
DNNUserController.ChangePassword(objUser, objUser.Membership.Password, passwordToValidate)

To
DNNUserController.ChangePassword(objUser, DNNUserController.GetPassword(objUser, ""), passwordToValidate)

it looks like in DNN6, objUser.Membership.Password is now returning a null (maybe some security thing??), which causes the 2nd parameter to be null, which causes the ChangePassword method to have an uncaught exception. The GetPassword method I swapped in still returns the current password, so implementing this change, the function now does not bomb.

Hope this helps.

 
New Post
9/7/2011 4:01 PM
 
Anyone have a workaround that doesn't require a change to code?  We're having the same/similar issue - see synopsis below.
  - Jason

With the AD provider, some users are able to use the Windows option in the DNN Account Login module to log in one time only.  A DNN user account is successfully created during the initial login but subsequent logins with the Windows option of the Account Login module fail.

The same users are able to use the WindowsSignin.aspx login page to authenticate as needed, so this appears to be a provider or code issue & not a corrupt data issue.  Also, most of our users are able to use the Account Login module without problems - This only affects a few users.  There appears to be a pattern where this affects recently created Windows accounts, but we haven't been able to confirm if that's related.

DNN 6.0.0
Authentication 1.0.0
DNN_ActiveDirectoryAuthentication 5.0.2
DotNetNuke ASP.NET Membership Provider 6.0.0
.Net Framework 3.5, 4.0

DNN Event Viewer error:

AssemblyVersion: 6.0.0
PortalID: 0
PortalName: Intranet
UserID: -1
UserName:
ActiveTabID: 102
ActiveTabName: Login
RawURL: /Home/Login/tabid/102/Default.aspx?returnurl=%2fResources%2fEducation%2fServiceAcademy.aspx
AbsoluteURL: /Default.aspx
AbsoluteURLReferrer: http://intranettest/Home/Login/tabid/...
UserAgent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; MS-RTC LM 8; InfoPath.3)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 3172f6fd-fc71-4dcf-9cec-d095ff3d4f50
InnerException: Value cannot be null. Parameter name: oldPassword
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.Web.Util.SecurityServices.CheckPasswordParameter
StackTrace:
Message: DotNetNuke.Services.Exceptions.PageLoadException: Value cannot be null. Parameter name: oldPassword ---> System.ArgumentNullException: Value cannot be null. Parameter name: oldPassword at System.Web.Util.SecurityServices.CheckPasswordParameter(String param, String paramName) at System.Web.Security.MembershipUser.ChangePassword(String oldPassword, String newPassword) at DotNetNuke.Security.Membership.AspNetMembershipProvider.ChangePassword(UserInfo user, String oldPassword, String newPassword) at DotNetNuke.Entities.Users.UserController.ChangePassword(UserInfo user, String oldPassword, String newPassword) at DotNetNuke.Authentication.ActiveDirectory.AuthenticationController.RandomizePassword(UserInfo objUser, String& strPassword) 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.Button.OnClick(EventArgs e) at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument) at System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) at System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) --- End of inner exception stack trace ---
Source:
Server Name: INTRANETTEST

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationerrors with AD provider after upgrade to DNN 6.0errors with AD provider after upgrade to DNN 6.0


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out