- Full Description
With such wide accessibility, securing your code effectively needs to be a top priority. You will quickly find that the WCF security protocols youre familiar with from .NET are less suitable than they once were in this new environment, proving themselves cumbersome and limited in terms of the standards they can work with.
Fortunately, ASP.NET Web API provides a simple, robust security solution of its own that fits neatly within the ASP.NET MVC programming model and secures your code without the need for SOAP, meaning that there is no limit to the range of devices that it can work with if it can understand HTTP, then it can be secured by Web API. These SOAP-less security techniques are the focus of this book.
What youll learn
- Identity management and cryptography
- HTTP basic and digest authentication and Windows authentication
- HTTP advanced concepts such as web caching, ETag, and CORS
- Ownership factors of API keys, client X.509 certificates, and SAML tokens
- Simple Web Token (SWT) and signed and encrypted JSON Web Token (JWT)
- OAuth 2.0 from the ground up using JWT as the bearer token
- OAuth 2.0 authorization codes and implicit grants using DotNetOpenAuth
- Two-factor authentication using Google Authenticator
- OWASP Top Ten risks for 2013
Who this book is for
No prior experience of .NET security is needed to read this book. All security related concepts will be introduced from first-principles and developed to the point where you can use them confidently in a professional environment. A good working knowledge of and experience with C# and the .NET framework are the only prerequisites to benefit from this book.
- Table of Contents
Table of Contents
- Welcome to ASP.NET Web API
- Building RESTful Services
- Extensibility Points
- HTTP Anatomy and Security
- Identity Management
- Encryption and Signing
- Custom STS through WIF
- Knowledge Factors
- Ownership Factors
- Web Tokens
- OAuth 2.0 Using Live Connect API
- OAuth 2.0 From the Ground UpÂ
- OAuth 2.0 Using DotNetOpenAuth
- Two-Factor Authentication
- Security Vulnerabilities
- Appendix: ASP.NET Web API Security Distilled
- Source Code/Downloads
On page 27:The example for changing authorization from the web.config element to AuthorizeAttribute() filters neglects to mention that you need to add the [AllowAnonymous] attribute to the actions in the LoginController.
On page 28:The solution provided to overcome a 302 redirect on a web api call is correct, but adding the AuthorizeAttribute as a global MVC filter as shown on the page prevents the login page from being reached as well.