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,