sql server - one authentification for different applications -


i'm building 4 websites. should have same login-datas (user can registrate on website 1 , can use website 2 , 3 using same login-name).

my idea use ms sql membershipprovider (good idea?). don't know place sql-mebershipprovider (in databse? or websites? -> sound getting chaos^^)

a other idea i've read create webservice authentification?

but think i'm getting problems data consitency, because think there no way point 1 database other (linking example usertable in database 1 texttable in databse 2).

i want use mvc3 , ms sql-database.

any experiences or ideas? lot!

you can use separate membership database , point providers of each site @ database.

if wanted use role provider have have same roles in 4 websites may not want. use central database handle authentication , create local user record in each website links central user database (you have linking manually i.e. no relationship). let role own role provider each site.


Comments

Popular posts from this blog

c# - SharpSVN - How to get the previous revision? -

c++ - Is it possible to compile a VST on linux? -

url - Querystring manipulation of email Address in PHP -