Meeting MS DEV MTL du 14 Octobre 2014
Sujet: Introduction à ASP.NET Identity
Conférencier: Mathieu Richard
ASP.NET Identity qui a été livré avec Visual Studio 2013 est appelé à remplacer ASP.NET Membership et Simple Membership. Mathieu nous fera un brève introduction de l'historique et des raisons derrière ce remplacement. Ensuite nous verrons les différents cas d'utilisation (en code) ainsi que les possibilités qu'offre ASP.NET Identity.
Strategies for Landing an Oracle DBA Job as a Fresher
Mathieu Richard: Introduction à ASP.NET Identity
1. ASP.NET IDENTITY 2.0
Presented by Mathieu Richard mathieu.richard@gsoft-group.com / mathieu.richard5@gmail.com /
@matrichard5 / www.matrichard.com
2. | 2
Why YAMF*?
Membership Provider
The database schema was designed for SQL Server
System is designed around assumptions appropriate for a
relational database.
Log-in/log-out functionality is based on Forms
Authentication
Can’t use OWIN
Barely extensible
*Yet Another Membership Framework
3. | 3
Features
One ASP.NET Identity system
Ease of plugging in profile data about the user
Unit testability
Role Provider
Claims Based
Social Login Providers
Azure Active Directory
OWIN Integration
6. | 6
Resources & What’s next
http://www.asp.net/identity
http://odetocode.com/blogs/scott/archive/2013/11/25/asp
-net-core-identity.aspx
Implementing 2 factor auth.
DocumentDB implementation.
Working with Social providers API
The core identity abstractions are interface based and revolve around the concepts of users and stores.
These abstractions are more flexible and composable than the membership providers
Users are the people who are happy to authenticate themselves to your web application
stores are the components happy to persist and retrieve user information from a data source