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 ForumsAuthenticationAuthenticationWhat to know when you upgrade to AD loginsWhat to know when you upgrade to AD logins
Previous
 
Next
New Post
12/16/2009 9:54 AM
 

Hello,

I have no experience with dotnetnuke at all, but have some questions. Just curious if it is possible.
I have created a local DotNetnuke website. Just for testing the enviroment and evaluating the possibility's.
I have currently no active directory in use on the server that hosts dotnetnuke. Is it possible to connect to a other ad-server than the host?

And when i do does the roles i have created on this moment still be active and configurable? Or doesnt that work at all in combination with AD?

Also i want to know if i need to make changes to my own created modules? There modules who connect to a ms sql server and look in tabbles and databases that dont belong to dotnetnuke.

Thanks in advantage,

Stefan

 
New Post
12/16/2009 11:12 PM
 

Is the server on a domain? If so then it should be able to connect to the domain's AD. If it isn't then, sorry, it's not going to work.

I'm not sure what you're asking on your second paragraph but I'll give it a shot at answering.... Any roles you create stay there. If they happen to have the same name as an AD group then they'll be automatically populated, de-populated if the AD user belongs to the AD group.(or not).

You shouldn't have to make any changes to any modules. The provider is meant to be a transparent interface that allows your AD users to login without having to create another account on DNN. If it works in a stock DNN install it should be no different once the AD provider is added.

 
New Post
12/17/2009 6:21 AM
 

That was completely what i ment. Thanks.
Just one more question since you are member of the AD project team

Mike Horton wrote
If they happen to have the same name as an AD group then they'll be automatically populated, de-populated if the AD user belongs to the AD group.(or not).

What if the groups are in different OU's?

For example:
the Domain example contains several OU's
the OU org contains several ou's including groups where the groupfiles are placed
the OU usr contains the departements OU's where the employees of a departement are placed.
These employees are member of the groups in the groups OU in org.

If i want to use the same name do i need to give the roles the name containing the OU's ,for example: org\group\pr, or will pr be enough?

Thank you in advantage,
Stefan

 
New Post
12/22/2009 1:29 PM
 

It shouldn't matter what OU the groups are in, as long as they are part of the same AD tree in the AD forest. 

As for duplicate groups, even if  they are in different OUs two groups cannot have the same name.  Sure they can have the same AD name, but the "pre-Windows 2000" group name (the one DNN uses)  has to be unique in the AD tree.  Since 99.99% of the people use the same name for both, you shouldn't run into a duplicate name problem because you cannot create one.

 

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationWhat to know when you upgrade to AD loginsWhat to know when you upgrade to AD logins


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