I'm going to be making my own profile provider for the following reason:

I have a Single Sign On scenario where users will edit their profile on a central site (and on a separate DNN application).  Client portals will be able to have read only access to profile settings provided by the centrail site.  In addition to these which remain consistent through all DNN portals that are a member to this single sign on service - profile properties can be added at the "child" portals that are specific only to that portal.  Only these specific properties can be written to on that portal itself.

I think I'm looking at re-writing the DNNProfileProvider so that it gets its data from two different databases (and eventually one database and one webservice) and merges that data into the object that contains profile information...  I don't know how i'm going to implement the readonly functionality - worst case senario at the provider level changes are just ignored to "centralized" properties.

Has anyone else done anything like this; or made significant changes to the profiles are of the code who might be able to give me some advice?

This is the last peice to my industry specific "roaming personal profile" single sign on service.  I have the authorization and authentication working flawlessly (in pre-production tests).. I've been saving this part for last

Thanks for the advice,

Matt Christenson

www.RealSkydiving.com