I am creating a new middle tier where all our customer calls will go through the WCF service. We use ASP.NET membership in the service to authenticate users. The middle tier will fall into the existing database, in which we already have an InetUsers table containing usernames and passwords.
Here he begins to get confused. This new middle tier will be used by our web application, but not our existing desktop application, which until we rewrite it at some point in the future will not use the old middle tier COM +. User administration for the web application is done in the desktop application. In other words, users will be created, and passwords will be set and changed from the desktop application, which, in turn, will fall into the existing InetUsers table.
Ideally, when we deploy a new middle tier, we take all the users from the InetUsers table and create entries for them in aspnet_Users and aspnet_Membership. Then we set the trigger in the InetUsers table to update aspnet_Users and aspnet_Membership.
A whole bunch of questions are collected in it, so I will try to list them all here:
- Is this the right approach? Obviously, this data is not ideal in two places, but keep in mind that here I am not the ultimate director, and we, at least, are now lingering on some kind of legacy. However, there may be a better way.
- In the same vein - are we better off coding our membership provider rather than using SqlMembershipProvider? How difficult / easy is it to do?
- , aspnet_Membership_XXXX , . , , aspnet_Membership_CreateUser SQL (.. ...) API, , . ?
- - , ?
.