Using SqlMembershipProvider I can set up an SQL server account and use all the feature as decribed.
Now I want to centralize user account management at an ENTERPRISE level. ie. Accounts will be created and managed by a seperate app.
All other apps will have READ_ONLY access the the SqlMembershipProvider tables.
When I setup up another account with only READ_ONLY access to the tables, I cannot use any of the feature anymore. The apps will need to use the tables to
1) Validate Users
2) Get their Roles
The app account has READ/WRITE permisions to aspnet_Membership table
The app falis consistently. How should I setup an SQL-Server account that will allow essentially read only access to the tables and not be able to alter any data to the enterprise-level tables? (Except, LastLoginDate etc) It cannot ValidateUser etc.
...
Go to the complete details ...