Security and cryptography are important to most applications. It can often be difficult to know how to correctly implement these features in your applications; especially to make the implementation be easily reusable and swappable. In this course you will learn how to use the Security Application Block to cache user credentials for future use and authorize users from various sources. You will also learn how to use the Cryptography Application Block to properly secure sensitive information.
Security Block Overview and Configuration Hi. This is John Sonmez from Pluralsight, and in this module we're going to be looking at the security application block from the Microsoft Enterprise Library, and we're going to see how to configure it. Now, the security block is not a very large block compared to some of the other application blocks, so we'll actually be covering in just two modules. A security block is relatively small. We're going to cover what the block does and what the functionality of the block is, and we're going to look at how you might use the security block and why you might use this in your application. We're going to take a look also at a tool called AzMan, or Authorization Manager, and that tool is going to be used by the security block, or it's an option that you can use with the security block in order to configure your authorization. Then finally, we'll look at configuring using the Enterprise Library configuration tool to configure the security block.
Using the Security Block Hi. This is John Sonmez from Pluralsight. And in this module, we are going to examine using the security block from the Microsoft Enterprise Library. In the previous module, we had gone over the security block and what it can do. But in this module, we're going to actually use it in some code, and we're going to see how to actually cache a user's credentials; to get those credentials back from the cache, using a token; and then we're going to set up some rules for authorization and see how we can use the authorization manager to determine if a particular user is authorized, according to a rule that we specify. And then we'll look at some things like expiring the cache, so that we can flush a user's credentials out. And finally, we'll use the authorization manager -- or the AzMan -- to control access, instead of using the built-in authorization manager that stores the authorization rules in our configuration.
The Cryptography Block Hi, this is John Sonmez from Pluralsight, and welcome to the module on the cryptography block. In this module, we are going to be looking at the entire cryptography block. It's actually the smallest block of the Enterprise library, so there's not a whole lot to it, but it is still a very important block, because it can prevent us from making some critical errors that can really jeopardize security of our applications. We're going to start off by talking about the block in general and talking about the functionality that it has, and a little bit about why you need it, and then we're going to look at how to configure the cryptography block, and then finally, we'll dive into some code example and we'll see how we can do things like encrypt a string, using this block, decrypt that string and generate some hashes and work with those hashes.