ASP.NET MVC Best Practice for Authenticating and Saving Custom Auth While It Works

Question

I’m just investigating the problem and getting a lot of different suggestions, can anyone help include details on the topic

• existing methods
• limitations
• advantages and disadvantages
• attack defense

I am looking for an overview to get directions.

EDIT:

An audience is a user from all over the world who must register.

Answer 1

Throwing an answer here from some systems with which I had professional experience:

. / , , .

ASP.NET

MS, MVC, . , , , , , , / , , . , , . factory , . , , , , ( ). auth, . , , AD .

Windows Auth.

Windows , , - Active Directory . , , (weeeeee!), . , , , , . , , , . , , AD , .

/Windows

auth, auth- AD . , , , , . - auth, URL- . - , Active Directory, , cookie , MVC . MVC AD- ( N- ), , AD , . , , , AD, , , ( , .) , - , , , . , , , , . - - . DMZ AD. , , AD, reset, ..

, facebook, twitter, google - OAuth.

, , , , , - .

, "", .

Answer 2

ASP.NET MVC Framework, ASP.NET (Google, Facebook, Microsoft ..).

Visual Studio, ASP.NET MVC , Identity. , [] , .

Answer 3

, -

signalR, , , , .