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 ForumsAuthenticationAuthenticationPreventing the forest from seeing the treePreventing the forest from seeing the tree
Previous
 
Next
New Post
7/18/2006 12:26 PM
 

OK, the thread title's a little strange, but I'm trying to create a DNN page that's invisible to users on our parent domain. I've read through this forum but still can't figure out whether I have actually accomplished matching AD groups to DNN roles. 

I have automatic user login working on DNN 4.3.2 (running on a W2K3 server). Anyone who accesses DNN from either the parent domain or our child domain gets logged on. That bit works great. My test however, is going nowhere. I have done the following:

  1. Created a page called 'InvisibleToParentDomain'
  2. Created a DNN role called *ChildDomain*\Domain Users.  (The child domain AD user group *ChildDomain*\Domain Users appears to include everyone on the child domain. Anyone who logs in to DNN is automatically added to the DNN Users as *ChildDomain*\Username.
  3. On the 'InvisibleToParentDomain' page, checked the View Page permissions for the *ChildDomain\Domain Users* role.

What I expect - and understand is supposed to happen, from reading the thread in this forum - is that as long as the DNN role is called exactly the same thing as the AD group, the role should include all the users in that AD group. Therefore anyone logging in from the child domain should be able to see the page. However, the only person it shows up for is me as admin.

Can anyone tell what I'm doing wrong?

Thanks,

Gary

 

 
New Post
7/19/2006 10:14 AM
 
ggreen001 wrote

What I expect - and understand is supposed to happen, from reading the thread in this forum - is that as long as the DNN role is called exactly the same thing as the AD group, the role should include all the users in that AD group.

Can anyone confirm that if you create a DNN role called *domain*\Domain Users, it will (at least theoretically) synchronize with the AD group *domain*\Domain Users ? - So I know I'm not barking up the wrong tree...

 

 
New Post
7/19/2006 11:27 AM
 

Not likely until those users hit the site. AFAIK DNN doesn't go out and get a list of all the users in the AD. Only when someone comes and isn't found in the DNN DB is the AD polled to see if that users exists in AD. I think


Chris Hammond
Former DNN Corp Employee, MVP, Core Team Member, Trustee
Christoc.com Software Solutions DotNetNuke Module Development, Upgrades and consulting.
dnnCHAT.com a chat room for DotNetNuke discussions
 
New Post
7/19/2006 12:27 PM
 

Right, but once DNN had found that user in AD (ergo, that user must be part of the AD group *domain*/Domain Users), wouldn't it then make that user part of the *domain*/Domain Users role that I had created in DNN?

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationPreventing the forest from seeing the treePreventing the forest from seeing the tree


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