asp.net - Session based authentication -


i using session based authentication asp.net website.

1) know whether safe or not have session based authentication security purpose.

2) when number of users grows whether many session slows down performance?

3) in case nothing work out, end migrating session based authentication forms authentication, safe way migrate?

so far have referred link

http://www.asp.net/general/videos/how-do-i-create-a-custom-membership-provider

i know whether safe have session based authentication security purpose.

that depend on how implemented it, if storing logged in username in session should pretty safe.

when number of users grows whether many session slow down performance.

if using in-memory session provider mean storing inside memory of web server information logged in users. if application domain recycles, loose session information , logged in users automatically logged out not good. not scalable solution. might want use out of process session provider if ever decide go path.

in case nothing work out, end migrating session based authentication forms authentication, safe way migrate?

simply remove code relies on session , replace using user.identity.name fetch logged in user. here's nice overview of forms based authentication. that's recommended approach handling authentication in asp.net applications.


Comments

Popular posts from this blog

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

java - Output of Eclipse is rubbish -

jquery - Confused with JSON data and normal data in Django ajax request -