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 ForumsAuthenticationAuthenticationSame AD user in differ portalsSame AD user in differ portals
Previous
 
Next
New Post
10/25/2007 1:26 PM
 

I can. I'm still rying to resolve my problems from this post. http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/89/threadid/176780/scope/posts/Default.aspx

I can't for the life of me understand how to get a child portal to create and authenticate a user account from AD. However, if I make the entire parent portal require windows authentication a windows account is generated even though I did not set up authentication on the parent portal.If I then browse to the child portal which does have AD authentication enabled, It doesn't add me to the portalusers table nor login me in.

My current setup includes:

DNN 4.6.2

Webconfig - commented and sometimes uncommented.<add name="Authentication" type="DotNetNuke.Authentication.ActiveDirectory.HttpModules.AuthenticationModule, DotNetNuke.Authentication.ActiveDirectory" />-->

Parent portal: anonymous

child portal: AD authentication, windowssignin.aspx set to windows authentication only.

IE 6.0 with no management capabilites due to group policy.

Browse to: http://myintranet/dnn/mychild - Note this path which is not a fully qualified path displays Local Intranet in IE

I get to the home page fine but I am not logged in. If I manually create the portaluser record I get logged in as the domain account.

 

 

<!--

 
New Post
10/25/2007 3:56 PM
 

I haven't found a fix yet but here are my observations from when I was trying to sort this out the other day. I'm going off of memory but with <add name="Authentication..../> uncommented a piece of code call OnAuthenticated_Request is called well before anything else AD related is called. Actually the procedure is called three times. The first time it has the correct url I believe (http://myintranet/dnn/child), the second webresource.axd, and the third ends up being something like http://myintranet/dnn/default.aspx. You may notice on occasion when you go to http://myintranet/dnn/child the url ends up looking like http://myintranet/dnn/default.aspx?alias=myintranet/dnn/child and that's where I think things are getting hosed. When a user normally clicks Login a fair amount of information is stored (PortalID, return url, etc) but with the automatic login it all takes place before a lot of that information has been collected and that's where things get screwed up. I've looked at trying to capture that info in OnAuthenticated_Request but the problem becomes how do I know if I've captured the right information. I do plan on talking with the Core team architects to get their insights and possibly they may have an idea that I haven't looked at yet.

I haven't looked at Authentication turned off on the parent and turned on on the child yet mainly because there's a bug in the current provider that doesn't allow it to be turned off. I've fixed that for a new release but forgot about the parent-no authentication/child-authentication scenario though I suspect the problem will still be there based on my observations above. However, this I do know works because it's how I tested things in your initial post. With Authentication turned on in both the parent and the child and with <add name="Authentication"..../> commented out it is possible to have AD authentication working on both the child and the parent out of the box. I'm not sure what will happen if some accounts have be automatically created in the parent portal already. My coding dev child site won't work properly when I try to manually login but I was trying different things and may have messed up the users tables. On my testing dev site I can manually login to both the parent and the child with my AD credentials but I did that without having run the sites with <add name="Authenticated".../> uncommented.

 
New Post
11/1/2007 1:29 PM
 

Mike Horton wrote

mecha, you shouldn't have to manually do that. It's automatic when the user goes to the portal. Can you verify that it isn't?

I can confirm this.   DNN will only allow the same USERID to associate with 2 different portal ID's.   After that you have to manually add each to the DB table.  There are 3rd party modules available for $$ which do the same thing.  IMHO this should be a function of the authentication, both for DNN and AD with the HOST option to allow single userid's on multiple child portals.

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationSame AD user in differ portalsSame AD user in differ portals


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