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

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Upgrade 4.3.3 User Passwords IssueUpgrade 4.3.3 User Passwords Issue
Previous
 
Next
New Post
7/21/2006 9:25 PM
 

I ran an upgrade from 4.0.X to the latest release in our development environment and ran into the following issue.  The upgrade went fine until I tried to log in with various superuser accounts.  None of them would authenticate.  I went to the database and all the accounts were in the database. 

Next I created a new user and made it a superuser in the database.  Logged in and tried to change the passwords for my original superuser accounts.  I get the exception below.  Any ideas?

AssemblyVersion: 04.03.03
PortalID: 0
PortalName: ########
UserID: 19
UserName: Test
ActiveTabID: 34
ActiveTabName: SuperUsers Accounts
RawURL: /Host/Superuser Accounts/tabid/34/ctl/Edit/mid/343/UserId/1/portalid/0/Default.aspx
AbsoluteURL: /Default.aspx
AbsoluteURLReferrer: http://client.trucomply.com/Host/Superuser%20Accounts/tabid/34/ctl/Edit/mid/343/UserId/1/portalid/0/Default.aspx
UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; .NET CLR 2.0.50727)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 8571ce81-80ac-498e-bb2d-c423befba554
InnerException: Bad Data.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.Security.Cryptography.CryptographicException.ThrowCryptogaphicException
StackTrace:
Message: DotNetNuke.Services.Exceptions.PageLoadException: Bad Data. ---> System.Security.Cryptography.CryptographicException: Bad Data. at System.Security.Cryptography.CryptographicException.ThrowCryptogaphicException(Int32 hr) at System.Security.Cryptography.Utils._DecryptData(SafeKeyHandle hKey, Byte[] data, Int32 ib, Int32 cb, Byte[]& outputBuffer, Int32 outputOffset, PaddingMode PaddingMode, Boolean fDone) at System.Security.Cryptography.CryptoAPITransform.TransformFinalBlock(Byte[] inputBuffer, Int32 inputOffset, Int32 inputCount) at System.Security.Cryptography.CryptoStream.FlushFinalBlock() at System.Web.Configuration.MachineKeySection.EncryptOrDecryptData(Boolean fEncrypt, Byte[] buf, Byte[] modifier, Int32 start, Int32 length, Boolean useValidationSymAlgo) at System.Web.Security.MembershipProvider.DecryptPassword(Byte[] encodedPassword) at System.Web.Security.MembershipProvider.UnEncodePassword(String pass, Int32 passwordFormat) at System.Web.Security.SqlMembershipProvider.GetPassword(String username, String passwordAnswer) at System.Web.Security.MembershipUser.GetPassword() 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.Modules.Admin.Users.Password.cmdUpdate_Click(Object sender, EventArgs e) at DotNetNuke.UI.WebControls.CommandButton.RaiseImageClick(Object sender, ImageClickEventArgs e) at System.Web.UI.WebControls.ImageButton.OnClick(ImageClickEventArgs e) at System.Web.UI.WebControls.ImageButton.RaisePostBackEvent(String eventArgument) at System.Web.UI.WebControls.ImageButton.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 ---

 
New Post
7/21/2006 10:40 PM
 
Found the issue.  I copied the key settings into the new web.config file incorrectly.
 
New Post
7/22/2006 3:33 AM
 

What setting you changed?

After upgrade from 4.3.0 to 4.3.3 I can not login any more.
In development.config or release.config only things that I change were connection string and objectQualifier.

Thanks,
Oliver

 

 
New Post
7/22/2006 8:51 AM
 

I installed a fresh copy of DNN 4.33 using an empty data base. The install completed correctly. When it completed neither the host or admin accounts could log in.  In the <system.web> section there are values for a validationKey and a decryptionKey. The installation instructions say the <appSettings> section needs the following keys MachineValidationKey, and MachineDecryptionKey. Even after the the values in the system.web section are copied into the appSettings section the host and admin logins do not work.  I do not have the same problem with other versions of DNN

How do I get DNN 4.3.3 to work?

 

 
New Post
7/22/2006 1:16 PM
 

Make sure that the new web.config machineKey settings are exactly the same as the settings in the old web.config.  I copied them in incorrectly and that caused my problem.  Essentially I was able to create new users, but none of my existing accounts could log in.  These keys appear to be used to encrypt and decrypt the passwords for accounts.  Thus if you have different settings, the new accounts won't be able to login.  Hope that helps.

<machineKey
        validationKey=""
        decryptionKey=""

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Upgrade 4.3.3 User Passwords IssueUpgrade 4.3.3 User Passwords Issue


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