Newtonsoft.Json 5.0.6

A simple implementation of OAuth 1.0a and OAuth 2.0 protocols only supporting the consumer serverside flow. Complemented by DotNetAuth.Profiles to make it more better.

Abstractions for reading `.deps` files.

ASP.NET Core middleware that enables an application to support any standard OAuth 2.0 authentication workflow. This package was built from the source code at https://github.com/aspnet/Security/tree/93926543f8469614c2feb23de8a8c0561b8b2463

ASP.NET Core support for JSON PATCH. This package was built from the source code at https://github.com/aspnet/JsonPatch/tree/3b485909ebec98d9437058dbcf45dac3ccd1f157

Azure Key Vault enables users to store and use cryptographic keys within the Microsoft Azure environment. Azure Key Vault supports multiple key types and algorithms and enables the use of Hardware Security Modules (HSM) for high value customer keys. In addition, Azure Key Vault allows users to securely store secrets in a Key Vault; secrets are limited size octet objects and Azure Key Vault applies no specific semantics to these objects. A Key Vault may contain a mix of keys and secrets at the same time, and access control for the two types of object is independently controlled. Users, subject to appropriate authorization, may: 1) Manage cryptographic keys using Create, Import, Update, Delete and other operations 2) Manage secrets using Get, Set, Delete and other operations 3) Use cryptographic keys with Sign/Verify, WrapKey/UnwrapKey and Encrypt/Decrypt operations. Operations against Key Vaults are authenticated and authorized using Azure Active Directory. Key Vault now supports certificates, a complex type that makes use of existing key and secret infrastructure for certificate operations. KV certificates also support notification and auto-renewal as well as other management features.