Redis and Azure Storage key protection repositories

- [Instructor] In the final new fear in one point one we're going to talk about is the addition of Redis or Azure Storage data protection key repos, and this allows keys to be shared across several instances of a web app. Prior to having these in one point one, you pretty much had to use a network share and a file repository. So some common scenarios, sharing authentication cookies, or probably more importantly, cross-site request forgery, or CSRF, protection across load balanced servers.

The packages required if you're going to use Redis is Microsoft.AspNetCore.DataProtection.Redis and Azure Storage. Same prefix, but .AzureStorage. Since I'm not running on a load balanced or have the sample hooked up to Azure Storage or Redis, we're just going to talk about it here. The full details of how to use this and implement both ends of the equation are at the link on your screen, but it's very simple to add in once you have the appropriate plumbing in place.

For Azure Storage, in the configured services note these both have to be added before the services.AddNBC line. You would just add in services.AddDataProtection() .PersistKeysToAzureBlobStorage with the URI. To use Redis, you just create a new connection multiplexer connecting to the appropriate URI, and then you'd say services.AddDataProtection().PersistKeysToRedis.

So that concludes our new features in one point one. Stay tuned, and we'll cover all the new features in ASPI Net Core 2.0.