cenny26 / techecommerce-server Goto Github PK

Storing Confidential Information Using Azure Key Vault:
Azure Key Vault is a service used to securely store and manage confidential information. Here is a step-by-step guide on how to use it:

• Create Azure Key Vault - first, create a Key Vault via Azure Portal and add all secret information there.
• Add Azure SDK to Project - add Azure Key Vault SDK to project. We can use Microsoft.Extensions.Configuration.AzureKeyVault NuGet package.
• Set Up Configuration - add Azure Key Vault to the configuration in the Program.cs or Startup.cs file:

public static IHostBuilder CreateHostBuilder(string[] args) =>
        Host.CreateDefaultBuilder(args)
            .ConfigureAppConfiguration((context, config) =>
            {
                var builtConfig = config.Build();
                var keyVaultEndpoint = builtConfig["AzureKeyVault:VaultUri"];
                
                if (!string.IsNullOrEmpty(keyVaultEndpoint))
                {
                    var azureServiceTokenProvider = new AzureServiceTokenProvider();
                    var keyVaultClient = new KeyVaultClient(
                        new KeyVaultClient.AuthenticationCallback(
                            azureServiceTokenProvider.KeyVaultTokenCallback));
                    
                    config.AddAzureKeyVault(keyVaultEndpoint, keyVaultClient, new DefaultKeyVaultSecretManager());
                }
            })
            .ConfigureWebHostDefaults(webBuilder =>
            {
                webBuilder.UseStartup<Startup>();
            });

• Storing Azure Key Vault Information in Configuration - we can store Azure Key Vault information in the appsettings.json or appsettings.Development.json file:

{
  "AzureKeyVault": {
    "VaultUri": "https://your-key-vault-name.vault.azure.net/"
  }
}

Dependencies in the Application layer must be refactored over time. In a project built on the Onion architecture, the Application layer must contain few dependencies. The dependencies must be coded under the service name in the appropriate layers and called in the handler classes in the CQRS pattern. Thus, the handler classes will be more readable, and the correct structure of our codes will be preserved in terms of architecture...

In the current project, I have built an architectural storage service using the benefits of object-oriented programming. It is possible to change the storage service in the project only with a configuration in the Program.cs file. I'd love to use the AzureService I've coded extensively here, as per the project's wishes, but the very high asking price for the Blob Storage Service in the Azure Portal discourages me from doing so. Therefore, until the end of the project, I will use LocalService out of necessity. Again, I have no doubt that I will use clean and meaningful naming for as many files as possible in the project. I'm hoping to use AzureService as storage in my project once I have an account in the Azure Portal at some point...