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 ForumsAuthenticationAuthenticationModules PermissionsModules Permissions
Previous
 
Next
New Post
2/1/2011 3:27 PM
 
Hello..
Would like to integrate our Intranet (internal DNN) site into our live DNN site as a child portal.  A button on the main page would take them to the child portal and the users would enter their AD credentials in to see the intranet site from externally to the internal network.

Have the AD module configured correctly and can log into the portal using my network credentials; no problems.

Into the child portal, I added a DNN security role by the name of "Domain Users"; should sync with AD, right?

I'm testing this on our development box.  I have two HTML modules and two custom modules.  One of the HTML modules is setup for permissions for Unauthenticated Users View; this will display information like the user must log in, etc.  The other HTML module and the two custom modules have "Domain Users" view permissions configured.

When I hit the home page, I see the HTML module configured for Unauthenticated Users.  After logging in using my AD credentials, I'm greeted by nothing.  The other HTML module nor the two custom modules are not viewable.

It appears as though the DNN "Domain Users" security role doesn't see the AD users.  Am I missing something?

Thanks.. -Jeff
 
New Post
2/1/2011 4:19 PM
 
I'd have to step through the code to see if Domain Users even comes up as a property that ADSI can see. I'm just checking the AD here at work (where I don't have full admin permissions) and the scope and type for Domain Users is grayed out. I'll have to try and check my home network to see if it's the same. If it is then I'd guess that because it's a required (by Microsoft) group that it may not get polled when the ADSI code (which is what the AD provider uses to talk to the AD) looks for the user's groups.

That said.... You say that you've got the module setup for Unauthenticated users and the other setup for Domain Users. Are you external users allowed to login? I.E. They have DNN accounts? If not then why not just set the permissions to Authenticated Users?
 
New Post
2/2/2011 11:42 AM
 
I didn't get a chance to check my home domain last night but I just ran LDAPBrowser (it's a quick tool that returns all the info pulled from the AD in one form) against my work domain this morning. Domain Users isn't part of the properties pulled for memberOf so that's why you're not seeing it sync in your DNN install. Looking through all the data pulled by LDAPBrowser the object Domain User doesn't appear anywhere.
 
New Post
2/2/2011 12:09 PM
 
Hello, 
Thanks for the reply.. Yes, we're creating our intranet site as a child portal from our main live site.  Currently, we're still on the development side of things for testing, etc.  Kind of a, can it be done type of scenario right now.
There are internal forms, etc which we'd like people externally to access whenever they wish.  If they're at work and on the network, they'd hit the same portal and be auto-logged into the intranet site and away they go.  So yes, if they're external, they'll log into the intranet site using the network credentials.  Both of these options work perfectly for us in testing; well, externally isn't really being tested, but Opera requests username/password in order to see the site and it'll log in using network credentials.
Hmmm, I wonder why it doesn't see the "Domain User" group.  I figured I'd try that as a DNN security group since every user created on the network is automatically assigned to that AD group anyway.
One way I got around this and got it to work was assigning the auto-assign checkbox to the Domain Users security group.  This way,  when the user logs in, their credentials are checked with AD and if it's good, then they're auto-assigned to the Domain User security group and they can see everything on the page.  Probably not the best security configuration, but it does seem to work.  But since these users are only being assigned vew permissions to the page and modules, I don't think there'll be too many issues.
Thanks.. -Jeff
 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationModules PermissionsModules Permissions


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