By mswatcher
via blog.maartenballiauw.be
Submitted: Aug 07 2012 / 09:19
If you are familiar with OAuth2’s protocol flow, you know there’s a lot of things you should implement if you want to protect your ASP.NET Web API using OAuth2. To refresh your mind, here’s what’s required (at least): OAuth authorization server Keep track of consuming applications Keep track of user consent (yes, I allow application X to act on my behalf) OAuth token expiration & refresh token handling Oh, and your API
Tweet
SaveShareSend
Tags: .net, cloud, frameworks, web design
Add your comment
