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 ForumsAuthenticationAuthenticationManual AD Login Causes InnerException: Bad Data (v2 Beta) Manual AD Login Causes InnerException: Bad Data (v2 Beta)
Previous
 
Next
New Post
1/14/2008 4:53 PM
 
Mike Horton


Joined: 7/16/2003
Posts: 4865

I will have to dig into the code to see what encoding is being used. I inherited the code, I didn't write it so I sometimes have to hunt for certain things. There's a code chance that any encoding is handled by the .NET Directory Services class in which case I may not be able to find out what it is. 

I do have an additional question though. What Authentication Type are you using under Admin->Authentication?
 
New Post
1/15/2008 7:36 AM
 
Dan Codispoti

Joined: 1/17/2006
Posts: 43

DotnetNuke Authentication =False

Active Directory Settings: Enabled = True, Hide Login Controls =False SynchronizeRole =True, Provider= ADSI, AuthenticationType = Delegation

IIS Security Settings: Enable anonymous access = false, Integrated Windows authentication = true, Digest authentication for Windows domain servers = true, realm is set to domain (eft.fiserv.net)

 

<!-- Forms or Windows authentication -->
<authentication mode="Forms">
<forms name=".DOTNETNUKE" protection="All" timeout="60" cookieless="UseCookies"/>
</authentication>
<!--
<identity impersonate="true"/>
<authentication mode="Windows">
</authentication>
-->
 
New Post
1/15/2008 11:45 AM
 
Mike Horton


Joined: 7/16/2003
Posts: 4865

Dan

Do me a favor and try the following:

In the web.config uncomment only <identitiy impersonate = "true" /> and change it to <identity impersonate="true" userName="domain\username" password="password" /> and also give the user the same rights to your DNN install that NETWORK SERVICE has. The user doesn't have to have any special rights on the domain (just a generic user). I'm not sure why it would make a difference if there's a cookie there or not but it might be worth a shot.

I didn't get a chance to look at the code last night but should have time tonight.
 
New Post
1/18/2008 10:52 AM
 
Dan Codispoti

Joined: 1/17/2006
Posts: 43

Mike,

Sorry it took me a while to get back to you I was out of work with a bug. I tried you suggestion and uncommented the identity and set the userName and password. I also updated the permissions on the application pool and the web folder to match the username but could not access the site after wards. I was getting challenged for my network credentials and after enter them received an HTTP 401 error. I checked the event logs on the server and Kerberos was receiving blank credentials.

I ran my test again this morning to confirm my findings and the existence of the cookie is causing the bad data error. The steps I used were after getting logged in automatically I selected the logout. Then I tried to manually login and received the bad data error. I then deleted the cookie from my workstation with the windows login page up and tried the windows login again and it work like a charm.

Thanks

Dan

 

 

 
 
New Post
1/20/2008 11:46 AM
 
Mike Horton


Joined: 7/16/2003
Posts: 4865

At this point Dan I don't have an answer for you. The only time I've seen this error was when I was running multiple portals on separate installs and switching back and forth between them. IE: I might be running a DNN 3 install on my dev system along with a DNN 4 install with separate passwords on the host account. That just an example. However this shouldn't be the case with your setup as you're not running separate portals based on your description.
 
 Page 2 of 3
Previous123Next 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationManual AD Login Causes InnerException: Bad Data (v2 Beta) Manual AD Login Causes InnerException: Bad Data (v2 Beta)


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