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 ForumsAuthenticationAuthenticationAD login error w/ 4.9.2 and 1.0.5 - supposedly fixed?AD login error w/ 4.9.2 and 1.0.5 - supposedly fixed?
Previous
 
Next
New Post
3/11/2009 4:56 PM
 

I'm running into the same error other people have, but theirs were all from months if not over a year ago, and mine's just happening now.  Host and other DNN accounts log in fine, but AD accounts get this message on first login attempt:

A critical error has occurred.
Unknown UserCreateStatus value encountered Parameter name: UserRegistrationStatus

and this message on subsequent logins:

A critical error has occurred.
Redirect URI cannot contain newline characters.

I have uninstalled and reinstalled the provider, checked the settings, tried w/ and w/o role sync enabled.  I have two separate instances of DNN on this server in two app pools, both running DNN 4.9.2 and AD 1.0.5.  The other one works fine, but this portal just doesn't want to work properly.

Any ideas?  I can't think of what's different and one and not the other with regards to this problem.

 
New Post
3/12/2009 12:15 AM
 

This is a bug that's reappeared due to a core code change that was done after the provider was submitted to the Release process. If you check Gemini you'll see that the bug has been reopened and will be fixed in the next release.

 
New Post
3/12/2009 10:29 AM
 

Okay... in the meantime, does downgrading to 1.0.4 solve anything?  Why would this be a problem on one installation of 4.9.2 and 1.0.5 and not another?  Hmmm...

 
New Post
3/12/2009 10:45 AM
 

No downgrading won't make a difference because it was a change in the core code. When a user manually logs in it looks for a specific answer from the core code on whether the user was created or not (UserCreateStatus) and the expected answer has been changed. It will only happen the first time a user tries to manually login (if their account doesn't already exist in DNN). The account is still created it's just the answer that it expects is wrong.

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationAD login error w/ 4.9.2 and 1.0.5 - supposedly fixed?AD login error w/ 4.9.2 and 1.0.5 - supposedly fixed?


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.