Products

Solutions

Resources

Partners

Community

About

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

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Single-Sign-On by using Membership systemSingle-Sign-On by using Membership system
Previous
 
Next
New Post
4/4/2006 11:21 AM
 

I am new to DotNetNuke and I wanna develop my own Single-Sign-On module so that we can share our other local databse for authentication and authorization for security purposes, and also import/export data from other SQL Server data base

 

In version 4.0.2, how can I use another database to hold the user information while still using the membership functionality in DotNetNuke. I have already looked at the Doc that comes with dnn. While it describes how the new provider is integrated into DNN. I cant seem to see how to switch to another data store.

 

Please tell me from where i start and please forward any usefull link like tutorial telling detail about about situation

Is this possible.

 

thanx in advance

 
New Post
5/4/2006 12:35 PM
 
I have the same requirement. DNN looks like it exactly what we need, but we already have users and roles in another database that can't be converted to DNN.  All of our other software uses it.  This is the only thing keeping us from implementing DNN :(
 
New Post
5/4/2006 6:30 PM
 
This is possible, but you will need either a good amount of technical procifiency or the willingness to pay for this feature.  What you need is a custom membership provider.  By writing a custom httpmodule, you can authenticate against whatever user store you want.  If you go this route, I would encourage you to only use your  other db to authenicate and acquire user credentials.  Then, when you get to DNN, go ahead and insert/update/etc the user profile info in the dnn users and aspnet_users tables.  The advantage to doing this is you retain all the built-in DNN user features.
 
New Post
5/5/2006 3:01 AM
 

hi dears, 

We really have to wait for the next DotNetNuke Versions of 4.1 which will haver custom providers, As Core team rewriting the implementation, and I think DotNetNuke 4.1 version is expected at least a month out for public release.

http://www.dotnetnuke.com/Default.aspx?tabid=908

 

 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Single-Sign-On by using Membership systemSingle-Sign-On by using Membership system


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