Last post Sep 11, 2017 09:19 AM by carlakawill
Sep 11, 2017 08:54 AM|carlakawill|LINK
Does anyone know how to appropriately configure a SQL database user to access all the necessary SQL membership sp's/tables/views....? I have installed SQL membership in a SQL server database but i need to created a SQL user which my web application will
use to connect to the database and do whatever it needs to do. Seems straight forward enough but i couldn't find any documentation from Microsoft about this.
Sep 11, 2017 09:08 AM|PatriceSc|LINK
Seems you are looking for the membership API at
For a start you could create a page that creates a hardcoded test user. To be on the safe side note that it handles user accounts for your application. It doesn't handle the account used by your application to connect to the database (which would be my understanding
for a "SQL user").
Sep 11, 2017 09:19 AM|carlakawill|LINK
Its the SQL User for the application itself i need to configure. When installing SQL Membership its creates a number of object in the database all proceeding with "dbo.aspnet_". My question is how should i configure a SQL user account which can use those
objects which can then be used by my application. Creating user accounts for the application i found to be really easy but in testing the SQL User i created for the database connection i gave db Owner temporarily to test it but that is obviously not suitable
for production. Normally when creating a database i would assign a user a role which could give them all the permissions they need but SQL Membership creates several roles which if assigned still don't give the user enough rights to even authenticate.