Regardin different type of authentications exist in asp.net

Question

i am only familiar with form authentication. so tell me what others authentication scheme exist for mvc project which we can use ?

what is claim based auth ?

claim based auth is 3rd party auth system ?

we can implement in web site like form auth ?

if claim based auth is 3rd party auth then how it is different from open id or open auth system like facebook, google auth provider.

we use membership or identity to validate user and after validation give user permission to access protected pages . so tell me membership or identity is one kind of advance form authentication or is it totally different technology ?

i heard various term regarding authentication like form auth, token auth, identity, membership, open id, open auth, oauth, social login system. i am very much confused about those term. i want to know briefly about them and also like to know how they work and how they are different from each other.

i search google a lot but not getting any right tutorial which explain all above auth related term properly. so i need some one's help who would nice explain all the above terms and also explain how they works and how they are different from each other. also explain when people use which one.

looking for guidance. thanks

Answer 1

The ADO.NET Entity Framework allows developers to choose any one approach among three possible approaches: Database First, Model First and Code First.<br /> <br /> <strong>Database First:</strong> It is a more data-centric design that is based on an existing database. The Entity Framework is able to generate a business model based on the tables and columns in a relational database. The information about our database structure (store schema), our data model (conceptual model), and the mapping among them is stored in XML in an .edmx file.<br /> <br /> <strong>Model First:</strong> In this approach, we don't have an existing database and the Entity Framework offers a designer that can create a conceptual data model. It also uses an .edmx file to store the model and mapping information. When the model has been created then the Entity Framework designer can generate the database schema that can be used to create the database.<br /> <br /> <strong>Code First:</strong> Whether you have an existing database or not, you can code your own classes and properties that correspond to tables and columns and use them with Entity Framework without an .edmx file. In this approach Entity Framework does not leverage any kind of configuration file (.edmx file) to store the database schema, because the mapping API uses these conventions to generate the database schema dynamically at runtime.

Answer 2

Code first

• Very popular because hardcore programmers don't like any kind of designers and defining mapping in EDMX xml is too complex.
• Full control over the code (no autogenerated code which is hard to modify).
• General expectation is that you do not bother with DB. DB is just a storage with no logic. EF will handle creation and you don't want to know how it does the job.
• Manual changes to database will be most probably lost because your code defines the database.

Database first

• Very popular if you have DB designed by DBAs, developed separately or if you have existing DB.
• You will let EF create entities for you and after modification of mapping you will generate POCO entities.
• If you want additional features in POCO entities you must either T4 modify template or use partial classes.
• Manual changes to the database are possible because the database defines your domain model. You can always update model from database (this feature works quite good).
• I often use this together VS Database projects (only Premium and Ultimate version).