My users presently have a user name and password on our DNN website. I wanted to use those existing accounts with BugNET. I wrote a membership provider that would access the DNN account information.
This seemed to work at first. I was able to log into the website using my DNN website credentials. I could update my profile. However, when I attempted to modify roles for users I quickly received an exception regarding a null UserId. After some research, it appears that the those stored procedures accept a user name and link that to the membership Users table to get the user's identification guid.
It would be a great update to change the application to use the membership provider's ProviderUserKey property in those stored procedures. That would remove the hard link to the Users table and allow others to extend the membership provider and use user names and passwords from other databases.
Dan
This seemed to work at first. I was able to log into the website using my DNN website credentials. I could update my profile. However, when I attempted to modify roles for users I quickly received an exception regarding a null UserId. After some research, it appears that the those stored procedures accept a user name and link that to the membership Users table to get the user's identification guid.
It would be a great update to change the application to use the membership provider's ProviderUserKey property in those stored procedures. That would remove the hard link to the Users table and allow others to extend the membership provider and use user names and passwords from other databases.
Dan