Home

ConfigCore

Secure, centralized configuration for .NET CORE applications

• API Client Configuration Source
• SQL Server Client Configuration Source
• Encryption of sensitive configuration data at rest
• Support for additional host environment names

ConfigCore.ApiSource - API Configuration Source/Provider

Custom IConfigurationProvider uses an HTTP client to retrieve configuration data from a REST API. Extension methods on IConfigurationBuilder are used to add the API Configuration Source to the IConfigurationBuilder prior to calling Build. When the configuration is built, the API Provider will use an HTTP Client to retrieve key/value settings pairs from the API and add them to the configuration like any other configuration provider.

ConfigCore.DbSource - Database Configuration Source/Provider

This custom configuration provider sources configuration data directly from a SQL Server database. Table and Column names follow convention-based defaults for ease of configuration, but may also be overridden for flexibility.

Cryptography Features - Encrypt / Decrypt App Settings

ConfigCore uses Microsoft Data Protection to encrypt sensitive configuration data prior to storage in the configuration source. The configuration settings are decrypted by the client after the configuration is built.
ICryptoHelper - Provides low-level encryption and decryption functionality, and methods for managing the encrypted value prefix.
CryptoConsole - Sample interactive console application that uses ICryptoHelper to encrypt strings that can later be decrypted by ConfigCore clients.

Environment Features - Custom Environments

ConfigCore provides support for three custom application environments in addition to the .NET CORE standard environments

• Local
• Test
• QA

Samples - Preconfigured examples

Pre-configured APIs, Clients, and complete quickstart solutions are provided to demonstrate all features.