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 ForumsAuthenticationAuthenticationIntranet - Portals vs. PagesIntranet - Portals vs. Pages
Previous
 
Next
New Post
9/8/2008 2:36 PM
 

We are setting up an intranet site using DNN. I have enabled AD Authentication on the main portal. I have created child portals for some of our departments. I want a user to log on to the main portal, then click on a link that navigates them to their department, automatically log in based on the credentials supplied to the main portal, and access data accordingly. I have seen some SSO modules but most are quite expensive. Is having portals per department a good idea or more of a headach (mess)? My idea is to have the site setup similar to WSS...

 
New Post
9/8/2008 10:54 PM
 

Hello Raymond,
I was in a similar situation, except I had to create a customer extranet.  DNN is working great in this instance, but I had to break a unique constraint in the UserPortal table in order to grant a single user to multiple tables.  In order to let a user switch to different portals, I created a real simple module that queried which portals a user had access to and then displayed the results in a dropdownlist.  The dropdownlist then redirected the user to the appropriate portal.  As long as the children portals are set up to authenticate in the exact same fashion as the parent, my users do not have to re-login.  Hope this helps.  Feel free to reach out if you'd like to see my module.


-- Scott Allender
http://www.scottallender.com
 
New Post
9/9/2008 2:10 AM
 

In my testing with the AD provider this shouldn't be a problem. The user is automatically added to the child portal (UserPortal table) when they visit the child site (as long as the authentication has been setup on the child portal). My question is how extensive are your individual department child portals going to be? Are they basically only one page or multiple pages? Who is going to administrate these child portals? You or are you going to assign a user to be the administrator for the individual portal?

If you're only going to be using one page per department then I'd personally just go with an individual page on the parent portal and make it only available to the users in that group. This can be quite easy to do if your users are broken up by department in your AD as you can create the DNN Security Role that matches the AD Group and the users are automatically added to that group when they log in. Let's say I've got the following AD groups (Sales, Marketing, Management, and Customer Support). All that needs to be done is for those DNN roles to be created and Synchronize checked in the AD settings. Then, in the one page per department scenario, as the administrator I can create the following menu items (Sales, Marketing, Management, and Customer Support) and set the View permissions on the page to the corresponding group. Then when the Bob who is in Sales logs in he see the Home page and the Sales page but not the other three, when Joe, who is the Marketing Manager, logs in he sees Home, Marketing, and Management, etc. You could also have multiple pages per department under the parent menu item so it doesn't necessarily have to be a one page per department scenario.

I guess what it really comes down to a couple of things....who's doing the administration on the pages/portals and how much freedom are you giving them? IE: you can setup Page Editors as well and those users can add/remove modules and edit the content on the pages they're an editor of. Ultimately, what's going to work best for you as the overall administrator. If you've got 30 or 40 departments then giving each department a page section on the parent portal is going to make the menu a bear for you as an administrator. If you've got a dozen or so then it shouldn't be too bad.

 

 
New Post
9/9/2008 8:12 AM
 

Makes sense. We have about 16 departments in our organization (county government). I was going to use WSS but the individual user cals would be too expensive. The only reason I was leaning towards departments is so that each department could have their own calendar, documents, etc. Another question I could ask myself is that, will the end-users even use these features? Some would, while others wouldn't touch it. I'm thinking that in each portal, one or more people could handle the editing portion of the content. I like the idea of creating roles and allowing AD to sych to them. When you mention groups, are you referring to actual groups in AD or Organizational Units? We use groups very little, not saying that it can't be done.

 
New Post
9/9/2008 10:48 AM
 

Actual AD Groups.

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationIntranet - Portals vs. PagesIntranet - Portals vs. Pages


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