Using aspnet_regsql.exe to Configure Windows Authentication on an Already Created Database
I have a database (using Microsoft SQL Server Management Studio Express) that is currently being used quite heavily in a functioning application. I am migrating this application to Windows Authentication and not my existing Basic Authentication System (or lack thereof).
The easiest way I know to set this involves using the aspnet_reegsql.exe file to set up some tables for me. This obviously creates its main tables like dbo.aspnet_Roles, dbo.aspnet_Users and dbo.aspnet_UsersInRoles.
There are tables named dbo.Users, dbo.UserRole, and dbo.UserRoleMapping in the current database. Many of the stored procedures currently written for this database are based on these tables.
Is there any gentle way to settle in the new tables that aspnet_regsql.exe will create? Perhaps it is creating configurations for these existing table names, and not what it should do?
Thanks in advance:)
It looks like you are mixing two different things. Windows Authentication is a way of representing your Windows login to the database. It runs in SSMS, connecting to the database using Windows Authentication. The application will indicate in the line:
Integrated Security=SSPI;
instead of username and password. Both of these options send the current Windows credentials to the database. An example of a Windows login is your computer \ chris.
On the other hand, aspnet_regsql.exe sets up a bunch of tables that allow for Microsoft's predefined authentication. For example, these tables are required to manage inputs . When using the aspnet_regsql controls, you usually work with forms authentication. You log in by entering your username and password in the web form. See this site for more examples of participation.
a source to share