Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

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 ForumsAuthenticationAuthenticationCould not load type Could not load type 'DotNetNuke.Security.Authentication.AuthenticationController'
Previous
 
Next
New Post
1/25/2011 4:06 PM
 
EZ


Joined: 1/25/2011
Posts: 3
I'm trying to convert from 4.5.5 to 4.9.5. I've even tried going stepwise to 4.6.2.

I've seen a bunch of these errors posted in the forum. I have a slightly different problem. It only throws this failure if it is an invalid login. Successful logins properly authenticate but if you enter the wrong username/password it throw this error.

I've tried disabling all Authentication references in the web.config and disabled from Host->Settings->Authentication and nothing.

I've been trying to resolve this for 2 days now and I've gotten nowhere.
 
New Post
1/25/2011 4:47 PM
 
Mike Horton


Joined: 7/16/2003
Posts: 4865
Is this happening with the default DNN provider or a different one? Did you get any errors when you did your upgrade? There was a major shift with the authentication providers in DNN 4.6.0. Up until then the authentication was all part of the core (i.e if you wrote a new provider it had to be injected into the core code). With DNN 4.6 it was pulled out as separate modules that talked to a code wrapper. That's why I ask if there were any errors on the upgrade.
 
New Post
1/26/2011 8:46 AM
 
EZ


Joined: 1/25/2011
Posts: 3
Everything is default (i.e. I didn't specifically get anything different than the upgrade code). There were no errors in the upgrade. It looked identical to the output shown on Mitchel Sellers' website . We have a custom signin module that basically changes the look and how stuff redirects, however; it still goes through the WindowsAuthorization function. Funny thing though is that a couple of the types are missing:

DotNetNuke.Security.Authentication.AuthenticationController
DotNetNuke.Security.Authentication.UserInfo
DotNetNuke.Security.Authentication.UserController

So anything stemming from DotNetNuke.Security.Authentication is throwing an "is not defined" error when I try to build my signin module.

The part that confuses/frustrates me the most is that this only occurs on failures. I've checked the AccessDenied page in ModuleControls and it's going to  Admin/Security/AccessDenied.ascx as it's supposed to.

Can you think of anything that has changed in 4.6 that would cause this specifically for failed logins? Successful logins have no problems.
 
New Post
1/26/2011 11:20 AM
 
Mike Horton


Joined: 7/16/2003
Posts: 4865
I don't have all the changes that occurred with 4.6 handy but my suspicion is that the problem is with your custom provider. It'll probably have to be changed to account for the changes to the authentication process. Without seeing your module it may be working fine on successful logins because it's using it's own processes to log users in but trying to use the old DNN procedures that don't exist anymore on login failures. As a test is it possible to pull that module from the process and see what happens when you login then?

FWIW there were changes in the provider process going from DNN 4 to DNN 5 so you'll have to make more changes to your custom module.
 
New Post
1/26/2011 8:36 PM
 
EZ


Joined: 1/25/2011
Posts: 3
In the end, you were correct. I reworked the custom module to get rid of all of the bad calls due to moving the authentication stuff around. Unfortunately this probably won't help anyone else on the forum. Thanks for your help, Mike.
 
 Page 1 of 1
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationCould not load type Could not load type 'DotNetNuke.Security.Authentication.AuthenticationController'


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