Introduction
Digital certificates play a crucial role in web security. If you work as a web developer then you’ve probably come across at least some security related project where you had to deal with certificates in code.
Certificates come in a couple of different versions depending on their function, the most pervasive of which probably being server side ones for SSL connections. We’ve gone through server side certificates in some detail before on this blog starting here. In this series we’ll concentrate on client certificates and see what role they can play in web security. Most of the material on server side certificates, especially the first 2 posts are also relevant for this discussion.
It’s important to note already now that you can combine a number of security levels and solutions in your projects:
- You can have the traditional forms based authentication. You can read about it on this blog here and here.
- Custom authentication. Here‘s a series dedicated to custom auth in Web API 2 as an OWIN/Katana component
- Server-side certificates, see the reference above
- Client-side certificates, to be discussed in this series
- Various techniques related to cryptography, such as asymmetric encryption. You can check out the section called “Security and cryptography” on this page for inspiration.
…and there are probably many more options not listed here. The point is that these techniques can be combined, you are not restricted to just using one of them.
Read more of this post
Like this:
Like Loading...