any method to close the connection forcefully.
var microsoftSqlConnectionInfo = new MicrosoftSqlConnectionInfo
{
ConnectionString = "server=localhost\sqlexpress;port=1433;user id=sa;password=**;database=master;app name=vault",
MaximumOpenConnections = 5,
VerifyConnection = true
};
await vaultClient.MicrosoftSqlConfigureConnectionAsync(microsoftSqlConnectionInfo, mountPoint);
as on last line application throw following exception "System.Exception: '400 BadRequest. {"errors":["Error validating connection info: failed to send SQL Batch: write tcp [::1]:9468-\u003e[::1]:1433: wsasend: An existing connection was forcibly closed by the remote host."]}"
var microsoftSqlConnectionInfo = new MicrosoftSqlConnectionInfo
{
ConnectionString = "server=localhost\sqlexpress;port=1433;user id=sa;password=**;database=master;app name=vault",
MaximumOpenConnections = 5,
VerifyConnection = true
};
await vaultClient.MicrosoftSqlConfigureConnectionAsync(microsoftSqlConnectionInfo, mountPoint);
as on last line application throw following exception "System.Exception: '400 BadRequest. {"errors":["Error validating connection info: failed to send SQL Batch: write tcp [::1]:9468-\u003e[::1]:1433: wsasend: An existing connection was forcibly closed by the remote host."]}"
define a connection string, define roles, create credentials.
the library has no control or knowledge over the closing of the connection etc.
I was having some trouble running VaultClientEnd2EndTests so I tried my hand at refactoring
The vault server configuration is now in code and the only assumption about the VaultClientEnd2EndTests is that the currently supported vault.exe is in the bin/Debug folder of the testing solution
Here is the MR: rajanadar/VaultSharp#45
I abstracted the setting up of a test vault instance into it's own class and refactored the VaultClientEnd2EndTests to use this class. I'm hoping to build more End2End tests using this abstraction: https://github.com/rajanadar/VaultSharp/pull/46/commits
i was going through the https://www.vaultproject.io/ i do not see any
@andrewhart098 thanks for the offer. Right now, I redesigned VaultSharp for modularity & did the 0.10.x release. I expect the design to be stable now and keep adding new features on this design. Need to get a .net 1.x, .net 4.5 support going. After that, feel free to add bit by bit to the lib.
@DotNetGeek2017_gitlab I am working on the support for .net core 1.x, .net 4.5 support etc.
the vaultsharp docs is here (more to be added) https://github.com/rajanadar/VaultSharp/blob/master/README.md
--
Platforms supported: .Net Core 1.0 above, .NET Framework 4.5 and above, Mono 4.6 above, Xamarin (mac, ios, android), UWP 10.0 and above etc.
Feature highlights: Supports all Auth methods, all Secret engines, several system apis, first class support for Consul, kv v1 and v2, enterprise vault apis, abundant intellisense, custom hooks to set web-proxy etc.
Get it here: https://www.nuget.org/packages/VaultSharp
VaultSharp Documentation: https://rajanadar.github.io/VaultSharp/
VaultSharp Documentation: https://rajanadar.github.io/VaultSharp/
--
@DotNetGeek2017_gitlab The latest release supports .Net Core 1.0.
do I have to sign the request by myself?
@rajanadar Hope you can provide some pointers; could not figure it out. Once i get a VaultClient after doing Github authentication; I did not see how to get the Vault Client token so that for the next calls (until the token expire) it will not need to relogin. Did not see an example, what am I missing?
@leowmjw Every instance of IAuthMethodInfo has a property called ReturnedLoginAuthInfo
Once you do even 1 authenticated vault api call using the library, the vault token will be available in this ReturnedLoginAuthInfo object.
So hold onto the reference of IAuthMethodInfo you use to create the Vault Client.
And by the way, the library is a little smart.. It doesn't "relogin" on every api call. I use a Lazy evaluator to get the Token only once. That token is reused for all successive calls. (till the app domain recylces or you reinitialize the vault client)
So please take that into account before you go and implement a "token caching"/"relogin mechanism" etc.
- When you initialize the Vault Client, nothing really happens. No login is performed.
- When the first Vault API call is requested, the login call happens and the token is stored in the library.
- For further API calls, NO relogin happens. The previous token is used.
This Auth Info is available in the IAuthMethodInfo object after step 2.
I am evalauting this library and wonder if the login / token storage you describe above would work well for me. I want to renew certificates every month or so, and I would prefer not to keep the auth token live for so long. Does it relogin when the token expired?
Hi @rajanadar thank you for your good work. A quick question and an update request.
Question: Why in KeyValueSecretsEngineV2Provider.cs line 23/57 is /data/ injected between path? --- "/data/" + path.Trim('/') --- What if it was set outside of the api to a different path?
Update Request: I think I have fallen into issue 61 and can see other interest also. Is that on the priority list?
Question: Why in KeyValueSecretsEngineV2Provider.cs line 23/57 is /data/ injected between path? --- "/data/" + path.Trim('/') --- What if it was set outside of the api to a different path?
Update Request: I think I have fallen into issue 61 and can see other interest also. Is that on the priority list?
Hi @rajanadar thank you for your good work. A quick question and an update request.
Question: Why in KeyValueSecretsEngineV2Provider.cs line 23/57 is /data/ injected between path? --- "/data/" + path.Trim('/') --- What if it was set outside of the api to a different path?
Update Request: I think I have fallen into issue 61 and can see other interest also. Is that on the priority list?
Never-mind the question. I assume that is the V2 difference. V1 is ok. The update is request is still valid
