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 ForumsAuthenticationAuthenticationMSSQL to AD in DNN 4.4.1MSSQL to AD in DNN 4.4.1
Previous
 
Next
New Post
3/6/2008 2:56 AM
 

HI All,

Good day to all and I hope you could help :-) 

To start with, the company i've been working for has been using DNN 4.4.1 using MS-SQL authentication which we implemented for 300 users. Until recently, AD using Windows 2003 Server was mandated on us just few months ago which left out our DNN site still authenticating to the DB. I have few questions for you and I hope you could share some light over our predicament:

1) Is it OK and possible to migrate authentication in our already working DNN 4.4.1 from MS-SQL to AD?
2) Is the AD provider in DNN 4.4.1 works with AD in Windows 2003 just ok?
3) Do I need to know any caveats in AD in DNN 4.4.1?
4) other things I should add in my checklist

Thanks in advance!

 
New Post
3/6/2008 11:16 AM
 

You'll have to do some testing to but....

  1. When you switch to AD when your AD users login with their credentials a new user account will be created in the following format (DOMAIN\username) so you'd have to adjust any special role assignments accordingly.
  2. The AD provider works fairly well in DNN 4.4.1 so you shouldn't have too many problems (setup is the very close to the same as it is for the current documentation so you could use that as a guideline).
  3. AD is provided in 4.4.1 (don't download the current project as it is for 4.6.0 and higher). One thing that it doesn't do well 4.4.1 is Role Synchronization (only does it the very first time a user logs in and their account is created). If this is a concern then I'd suggest downloading the DNN AD fix for 4.4.1 from my site (under DNN Modules @ http://dnn.gmss.org).
  4. If possible I'd try setting up a mirror install of your current DNN install and test on there first. If you run into problems feel free to post back here.
 
New Post
3/6/2008 2:15 PM
 

Thanks a bunch Mike,

I think your suggestion for a mirror install sounds good instead of doing AD in a flick of a switch (or a few typing of parameters in this context ). Now it occurred to me that the role assignments are possibly the ones that will give me a headache since the there are quite a number of users assigned to various custom roles.

Are the custom roles in the DNN DB still usable/assignable to AD accounts after switching to AD? For example if I have a "userA" in DNN MS-SQL with an authentication role assigned as "IT web admin", then with AD, UserA becomes CORPDOM\UserA, can I still assign the "IT web admin" role to CORPDOM\UserA from AD? or do I need to do everything in AD?

I'm not familiar with role synchronization yet - but i'll read over it and see if it has a major impact with my users. I'll post back here soon whether I've done it successfully or not.

 
New Post
3/6/2008 10:05 PM
 

Ummmmm Now you're testing my memory.  

I just did a quick test on my dev system using the DNN 4.6.0 version of the provider and local DNN roles weren't affected so it should be the same in DNN 4.4.1 (there isn't a major difference in the provider).

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationMSSQL to AD in DNN 4.4.1MSSQL to AD in DNN 4.4.1


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