3

Closed

WebSecurity should support setting the database schema

description

When calling WebSecurity.InitializeDatabaseConnection, it should allow setting the database schema used thereafter.

As stated in the post below, the only way to currently achieve this is by setting the default schema for the user, but that isn't always possible (i.e. hosting policies):
http://stackoverflow.com/questions/6244131/websecurity-initializedatabaseconnection-how-specify-a-db-schema
Closed Sun at 11:57 PM by eilonlipton
The next version of Web API and MVC will feature a new identity system that is far more customizable and less restrictive then the WebSecurity implementation. The new system is built from the ground up to enable custom scenarios such as this.

comments

HongmeiG wrote Jun 7, 2012 at 9:59 PM

There is no action for this group of people to take for this issue. Please report this to the right forum. Thank you.

** Closed by HongmeiG 06/07/2012 2:59PM

pranavkm wrote Jun 7, 2012 at 11:42 PM

Woops, incorrectly closed the wrong bug :)

danwalkerak wrote Dec 14, 2012 at 10:30 PM

This is a high impact bug for me.

alworks wrote May 9 at 1:16 PM

Try this:
WebSecurity.InitializeDatabaseConnection(connectionStringName: "ApplicationServices", userTableName: "MySchema].[User", userIdColumn: "ID", userNameColumn: "Username", autoCreateTables: true);
"MySchema].[User" did the trick.

Sign in to add a comment