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 ForumsAuthenticationAuthenticationStoring user information to multiple databases?Storing user information to multiple databases?
Previous
 
Next
New Post
4/7/2009 4:43 AM
 

We are facing the following situation: We have several databases with employee information, where some contain the same data (basic data like name, adress, date of birth, etc.) while others might contain additional data (e.g. our current intranet database also asks for hobbies, favorite books, etc.) Re-developing our intranet with DNN we would like to integrate all these datasources so an employee only has to update his data once. Authentication will be done with AD.

How can we achieve this? Do we have to develop our own authentication provider? Is there some "OnUserProfileUpdate" event in DNN which we could use to store the information to the other databases?

 
New Post
4/7/2009 5:24 AM
 

There are different options from SQL server triggers, a custom membership provider in business logic updating multiple data sources or unifying data storage in a single location for all your intranet. it depends on your use cases and the products used, to find the optimal solution.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
4/7/2009 7:43 AM
 

Thank you for the information so far, Sebastian. You mention three possible solutions: SQL server triggers, a custom membership provider or unifying data storage. Do you have any further information, examples, or similar on these topics? I am currently examining what exact products are used and how far they have to be integrated.

So far I can see, there are these products:

  1. the existing intranet database, which (at least partwise) still has to be used, storing basic personal information, additional "social" information (hobbies, favorite books etc.), educational information (degrees, etc.), job information (job descriptions, boss, etc.), payment information etc., but also ticket for the current internal business card order system
  2. an additional HR system where I am still finding out about the database used and if it provided interfaces or similar, holding almost the same information as the 1. mentioned database (maybe some additional) but is used for our headquarter
  3. the Active Directory which holds some basic information (user id, e-mail, name, but not much more)
  4. finally of course the DNN user profile

Use case so far should be:

  • authentication and basic information from AD
  • with email or user id from AD we can find out what user record from the other system belongs to the authenticated user
  • personal and job information are received from and stored to 1. and 2.
  • DNN holds the user profile picture and additional "social" information (hobbies, favorite books, etc.)
 
New Post
4/20/2009 11:07 PM
 

Okay, so the major issue is to synchronize the fields from the userprofile with that in an MS SQL database, so if a user edit his user information in DNN, they should be updated in that MS SQL database too. Does anyone know a good way to achieve that?

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationStoring user information to multiple databases?Storing user information to multiple databases?


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