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 ForumsAuthenticationAuthenticationChild Portal AD not working correctlyChild Portal AD not working correctly
Previous
 
Next
New Post
6/13/2007 10:51 PM
 

Welcome back Mike,

Yes, I copied the new files to the directories. I thought things started working for me earlier but I was mistaken and had to retract an entry I added to the Gemini entry. I'm still adamantly plugging away at it though. I've gone as far as unregisterring myself from the parent and all child sites ensuring there is no trace of my DOMAIN\UserName in any of the tables and disabled Authentication. Once I did that I re-enabled Authentication on the Parent and (as host, restarted the application) and it auto logged me in for that site only. Neither Auto Login or DOMAIN\UserName logs me into any other site. Using my WindowsSignin trick posted earlier, it tells me incorrect password. If I try to register with DOMAIN\UserName it tells me there's alread an account with that name registerred.

Jon

 
New Post
6/15/2007 2:03 PM
 

I have found that I can get users working as desired in our porta/child portal implementation if I do the following:

1- create a link to windowssignin.aspx on the home page.  when users click on this they are recognized by DNN.

2 - the AD module leaves a blank display name, making it impossible to tell if DNN recognized the user.  I have created an insert trigger on dnn_Users that updates the display name.

3 - DNN does not make a user_portals record for any but the parent portal.  When I add a record for the child portal of interest, they are able to get to the portal.

4 - DNN only makes user_Roles records for Subscribers and Registered Users.  I have to manually add the user to the desired group in User_roles.  This is occurring despite the fact that I have turned AD integration on and created a DNN user role with identical name (including case) to the AD group I wish to synch it to.

At this point, users are able to access the child portal, and only see the content we configure.  This AD integration is critical for us as we are using it in our Customer Service group and have different modules on pages visible to our Sales vs. Tech users, with some modules visible to all.  We can actually live with the blank display name, and missing user_portal record (fixing both with a trigger), but the user group synchronization is really critical, and would be a shame to have to maintain manually in parallel to our AD.

I will try copying windowssignin.aspx to the child portal folders and see if this resolves the need for the autologin link.

I am interested in providing whatever info or suggestions I can to help with this part of the project.

 
New Post
6/27/2007 4:46 PM
 

Just a thought. You can use one of several menu systems (inventua for example) to simulate a page being the home of a sub portal if you do not mind the entry always being the main page of the parent.  Would make child portals a bit harder to link directly to.

Makes pages a bit harder to add and the skin would have to be the same as the parent or changed on each page, but the security and roles would be much easier to handle.

 

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationChild Portal AD not working correctlyChild Portal AD not working correctly


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