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

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...username and password syncronisation username and password syncronisation
Previous
 
Next
New Post
11/6/2008 7:00 AM
 

Hi All,

I have been asked if it is possible to syncronise user names and passwords across three separate websites. Each site is hosted independently.

This is for an association with around 2000 members. Currently they have a dnn3 site, imis, a complex membership database with crummy web interface and events pro, an event management application with a simple web interface.

We want to have the same user names and log-ins for each database. This should be possible to set up. As members move between sites, they will need to log in again - this is ok - it gives them a feeling of extra security.

The problem we have is if users want to change their password, the password change needs to be passed over to the other sites and syncronised. A batch process or a webservice perhaps?

Has anyone done something like this before, is this a big job? Any help or suggestions will be welcome,thanks,

 
New Post
11/6/2008 3:22 PM
 

I assume you have access to the database and source code for each site.   I would suggest taking a look at database triggers as one possible solution. The problem you are going to run into is that most likely you have your Dotnetnuke installation setup to encrypt the password so you are going to have to take that into account as well.  

Stuart


Hilbert Solutions, LLC
Owner, Hilbert Solutions, LLC
http://www.HilbertSolutions.com
A DNN Service Provider
From Module Development to DNN Upgrades, your one stop DNN Shop
 
New Post
11/6/2008 3:46 PM
 

Are they already set up on all 3 sites?

Do they already have the same username on each site?

Are they using the default DNN method/profile for changing their password?

I've never done this, but it will probably require some custom coding.

 

(this is me brainstorming)

The base of how I'd acomplish this is write a module or webservice. This module/webservice would call the module(page)/webservice on the other two sites and pass the username (assuming they are the same already) and/or email (if you have email set up to be unique on each server) along with the new password (encoded).

When the module/webservice recieves a call (I'd set up specific IP's that new passwords are accepted from) it gets the user by either usename/email and updates their password to the new one.

 

That's a quick idea of how I'd start looking at trying to accoplish synched passwords between DNN sites.

 

 
New Post
11/6/2008 5:49 PM
 

How about using OpenID for athentication on all 3 portals?


Joao Beltrao
IT Manager
Desejo Sem Limites Multimedia
PORTUGAL
View João Beltrão's profile on LinkedIn
 
New Post
11/7/2008 2:49 AM
 

Thanks for your suggestions. To answer some of your questions,

Stuart, sorry I was not clear in my post, there is only one DNN site, the others are asp.net web interfaces built onto client server systems. IMIS and one called events pro. At this stage I don't have too much info on them (no source at this stage), but assume (hope) I can do some sort of batch update of passwords using DNN as the primary user interface for password updating. My understanding is that DNN stores a hash or similar for passwords and compares it at log in. It is not possible to get raw passwords out of the db, major security exposure.

Baatezu, all the sites are running. The membership(users) are not loaded into the DNN site. It is a brochure site, but will become a premium content site for members.

We will assign membership id numbers as the user name, but want to give people to the opportunity to change their passwords.

We are planning to use DNN as the method to change passwords and then propogate the passwords to the other sites.

Ref the webservice idea, sounds good. Like the idea of using specific IPs to prevent hacking. Is this secure enough?

Joao, like the idea with openid. My hunch it the other sites are too basic for this however.

Anyone any experience with the webservice idea?

My other idea is some kind of encrypted email that gets sent to the other sites. Any thoughts?

Thanks,

 

 

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...username and password syncronisation username and password syncronisation


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