Define Request From Local Cerificate

[HorizonSecuritySRL]

In my use case I need to validate a certificate that resides in the local machine in order to ensure the correct communication with Vault placed on a host machine reachable on https.

To do this I introduced a new property in the VaultOptions that will be started with the path of the certified.

Within the VaultHttpClient class I inserted a method that initializes HttpClient with the result of the HttpClientinitialization () method which, in case the property is populated, passes the hundler parameter to HttpClient, thus specifying the certificate to be used with X509Certificate2. Otherwise the behavior of the plugin will remain unchanged.

I report the scenario with which the test was conducted:

public static async Task<Dictionary<string, string>> VaultAsync(string secretPath)
{
VaultOptions.Default.CertPath = new DirectoryInfo(
Path.GetFullPath(Path.Combine(Environment.CurrentDirectory, @"...." + "AppData\cert.crt"))
).ToString();

var vaultClient = new VaultClient();
vaultClient.Address = new System.Uri("https://vault.personal.domain.com:8200");
vaultClient.Token = "token";
var secret = await vaultClient.Secret.Read<Dictionary<string, string>>(secretPath);
return secret.Data;

}

[chrishoffman]

Can you please describe your use case in the pull requests description and how this will solve it?

[chrishoffman]

Please provide the description of the change in the description of the pull request. This is the main README for the repository.

[chrishoffman]

We are moving away from support specific .NET runtimes to ensure compatibility. Please target .NET Standard 1.1. There is another pull request already that removes .NET 4.5 specific support.

[HorizonSecuritySRL]

In my use case I need to validate a certificate that resides in the local machine in order to ensure the correct communication with Vault placed on a host machine reachable on https.

To do this I introduced a new property in the VaultOptions that will be started with the path of the certified.

Within the VaultHttpClient class I inserted a method that initializes HttpClient with the result of the HttpClientinitialization () method which, in case the property is populated, passes the hundler parameter to HttpClient, thus specifying the certificate to be used with X509Certificate2. Otherwise the behavior of the plugin will remain unchanged.

I report the scenario with which the test was conducted:

public static async Task<Dictionary<string, string>> VaultAsync(string secretPath)
{
VaultOptions.Default.CertPath = new DirectoryInfo(
Path.GetFullPath(Path.Combine(Environment.CurrentDirectory, @"...." + "AppData\cert.crt"))
).ToString();

var vaultClient = new VaultClient();
vaultClient.Address = new System.Uri("https://vault.personal.domain.com:8200");
vaultClient.Token = "token";
var secret = await vaultClient.Secret.Read<Dictionary<string, string>>(secretPath);
return secret.Data;

}

[chrishoffman]

Can you please describe your use case in the pull requests description and how this will solve it?

[chrishoffman]

Please provide the description of the change in the description of the pull request. This is the main README for the repository.

[chrishoffman]

We are moving away from support specific .NET runtimes to ensure compatibility. Please target .NET Standard 1.1. There is another pull request already that removes .NET 4.5 specific support.

[HorizonSecuritySRL]

In my use case I need to validate a certificate that resides in the local machine in order to ensure the correct communication with Vault placed on a host machine reachable on https.

To do this I introduced a new property in the VaultOptions that will be started with the path of the certified.

Within the VaultHttpClient class I inserted a method that initializes HttpClient with the result of the HttpClientinitialization () method which, in case the property is populated, passes the hundler parameter to HttpClient, thus specifying the certificate to be used with X509Certificate2. Otherwise the behavior of the plugin will remain unchanged.

I report the scenario with which the test was conducted:

public static async Task<Dictionary<string, string>> VaultAsync(string secretPath)
{
VaultOptions.Default.CertPath = new DirectoryInfo(
Path.GetFullPath(Path.Combine(Environment.CurrentDirectory, @"...." + "AppData\cert.crt"))
).ToString();

var vaultClient = new VaultClient();
vaultClient.Address = new System.Uri("https://vault.personal.domain.com:8200");
vaultClient.Token = "token";
var secret = await vaultClient.Secret.Read<Dictionary<string, string>>(secretPath);
return secret.Data;

}

[chrishoffman]

Can you please describe your use case in the pull requests description and how this will solve it?

[chrishoffman]

Please provide the description of the change in the description of the pull request. This is the main README for the repository.

[chrishoffman]

We are moving away from support specific .NET runtimes to ensure compatibility. Please target .NET Standard 1.1. There is another pull request already that removes .NET 4.5 specific support.

[HorizonSecuritySRL]

In my use case I need to validate a certificate that resides in the local machine in order to ensure the correct communication with Vault placed on a host machine reachable on https.

To do this I introduced a new property in the VaultOptions that will be started with the path of the certified.

Within the VaultHttpClient class I inserted a method that initializes HttpClient with the result of the HttpClientinitialization () method which, in case the property is populated, passes the hundler parameter to HttpClient, thus specifying the certificate to be used with X509Certificate2. Otherwise the behavior of the plugin will remain unchanged.

I report the scenario with which the test was conducted:

public static async Task<Dictionary<string, string>> VaultAsync(string secretPath)
{
VaultOptions.Default.CertPath = new DirectoryInfo(
Path.GetFullPath(Path.Combine(Environment.CurrentDirectory, @"...." + "AppData\cert.crt"))
).ToString();

var vaultClient = new VaultClient();
vaultClient.Address = new System.Uri("https://vault.personal.domain.com:8200");
vaultClient.Token = "token";
var secret = await vaultClient.Secret.Read<Dictionary<string, string>>(secretPath);
return secret.Data;

}

[chrishoffman]

Can you please describe your use case in the pull requests description and how this will solve it?

[chrishoffman]

Please provide the description of the change in the description of the pull request. This is the main README for the repository.

[chrishoffman]

We are moving away from support specific .NET runtimes to ensure compatibility. Please target .NET Standard 1.1. There is another pull request already that removes .NET 4.5 specific support.

[HorizonSecuritySRL]

In my use case I need to validate a certificate that resides in the local machine in order to ensure the correct communication with Vault placed on a host machine reachable on https.

To do this I introduced a new property in the VaultOptions that will be started with the path of the certified.

Within the VaultHttpClient class I inserted a method that initializes HttpClient with the result of the HttpClientinitialization () method which, in case the property is populated, passes the hundler parameter to HttpClient, thus specifying the certificate to be used with X509Certificate2. Otherwise the behavior of the plugin will remain unchanged.

I report the scenario with which the test was conducted:

public static async Task<Dictionary<string, string>> VaultAsync(string secretPath)
{
VaultOptions.Default.CertPath = new DirectoryInfo(
Path.GetFullPath(Path.Combine(Environment.CurrentDirectory, @"...." + "AppData\cert.crt"))
).ToString();

var vaultClient = new VaultClient();
vaultClient.Address = new System.Uri("https://vault.personal.domain.com:8200");
vaultClient.Token = "token";
var secret = await vaultClient.Secret.Read<Dictionary<string, string>>(secretPath);
return secret.Data;

}

[chrishoffman]

Can you please describe your use case in the pull requests description and how this will solve it?

[chrishoffman]

Please provide the description of the change in the description of the pull request. This is the main README for the repository.

[chrishoffman]

We are moving away from support specific .NET runtimes to ensure compatibility. Please target .NET Standard 1.1. There is another pull request already that removes .NET 4.5 specific support.

[HorizonSecuritySRL]

In my use case I need to validate a certificate that resides in the local machine in order to ensure the correct communication with Vault placed on a host machine reachable on https.

To do this I introduced a new property in the VaultOptions that will be started with the path of the certified.

Within the VaultHttpClient class I inserted a method that initializes HttpClient with the result of the HttpClientinitialization () method which, in case the property is populated, passes the hundler parameter to HttpClient, thus specifying the certificate to be used with X509Certificate2. Otherwise the behavior of the plugin will remain unchanged.

I report the scenario with which the test was conducted:

public static async Task<Dictionary<string, string>> VaultAsync(string secretPath)
{
VaultOptions.Default.CertPath = new DirectoryInfo(
Path.GetFullPath(Path.Combine(Environment.CurrentDirectory, @"...." + "AppData\cert.crt"))
).ToString();

var vaultClient = new VaultClient();
vaultClient.Address = new System.Uri("https://vault.personal.domain.com:8200");
vaultClient.Token = "token";
var secret = await vaultClient.Secret.Read<Dictionary<string, string>>(secretPath);
return secret.Data;

}

[chrishoffman]

Can you please describe your use case in the pull requests description and how this will solve it?

[chrishoffman]

Please provide the description of the change in the description of the pull request. This is the main README for the repository.

[chrishoffman]

We are moving away from support specific .NET runtimes to ensure compatibility. Please target .NET Standard 1.1. There is another pull request already that removes .NET 4.5 specific support.

[HorizonSecuritySRL]

In my use case I need to validate a certificate that resides in the local machine in order to ensure the correct communication with Vault placed on a host machine reachable on https.

To do this I introduced a new property in the VaultOptions that will be started with the path of the certified.

Within the VaultHttpClient class I inserted a method that initializes HttpClient with the result of the HttpClientinitialization () method which, in case the property is populated, passes the hundler parameter to HttpClient, thus specifying the certificate to be used with X509Certificate2. Otherwise the behavior of the plugin will remain unchanged.

I report the scenario with which the test was conducted:

public static async Task<Dictionary<string, string>> VaultAsync(string secretPath)
{
VaultOptions.Default.CertPath = new DirectoryInfo(
Path.GetFullPath(Path.Combine(Environment.CurrentDirectory, @"...." + "AppData\cert.crt"))
).ToString();

var vaultClient = new VaultClient();
vaultClient.Address = new System.Uri("https://vault.personal.domain.com:8200");
vaultClient.Token = "token";
var secret = await vaultClient.Secret.Read<Dictionary<string, string>>(secretPath);
return secret.Data;

}

[chrishoffman]

Can you please describe your use case in the pull requests description and how this will solve it?

[chrishoffman]

Please provide the description of the change in the description of the pull request. This is the main README for the repository.

[chrishoffman]

We are moving away from support specific .NET runtimes to ensure compatibility. Please target .NET Standard 1.1. There is another pull request already that removes .NET 4.5 specific support.

[HorizonSecuritySRL]

In my use case I need to validate a certificate that resides in the local machine in order to ensure the correct communication with Vault placed on a host machine reachable on https.

To do this I introduced a new property in the VaultOptions that will be started with the path of the certified.

Within the VaultHttpClient class I inserted a method that initializes HttpClient with the result of the HttpClientinitialization () method which, in case the property is populated, passes the hundler parameter to HttpClient, thus specifying the certificate to be used with X509Certificate2. Otherwise the behavior of the plugin will remain unchanged.

I report the scenario with which the test was conducted:

public static async Task<Dictionary<string, string>> VaultAsync(string secretPath)
{
VaultOptions.Default.CertPath = new DirectoryInfo(
Path.GetFullPath(Path.Combine(Environment.CurrentDirectory, @"...." + "AppData\cert.crt"))
).ToString();

var vaultClient = new VaultClient();
vaultClient.Address = new System.Uri("https://vault.personal.domain.com:8200");
vaultClient.Token = "token";
var secret = await vaultClient.Secret.Read<Dictionary<string, string>>(secretPath);
return secret.Data;

}

[chrishoffman]

Can you please describe your use case in the pull requests description and how this will solve it?

[chrishoffman]

Please provide the description of the change in the description of the pull request. This is the main README for the repository.

[chrishoffman]

We are moving away from support specific .NET runtimes to ensure compatibility. Please target .NET Standard 1.1. There is another pull request already that removes .NET 4.5 specific support.