Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    daviddahan01
    @daviddahan01
    i'm some questions/issues . is it the right place to ask?
    Raja Nadar
    @rajanadar
    sure @daviddahan01 we can also talk via https://github.com/rajanadar/VaultSharp/issues/new
    MayaKhan12
    @MayaKhan12
    hello
    i have started working on vaultsharp but facing some issues plz help me
    MayaKhan12
    @MayaKhan12
    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."]}"
    Raja Nadar
    @rajanadar
    @MayaKhan12 the library exposes the apis supported by vault server
    define a connection string, define roles, create credentials.
    the library has no control or knowledge over the closing of the connection etc.
    MayaKhan12
    @MayaKhan12
    please tell me then how can we connect with vault (MSSQL) in C#
    daborg69
    @daborg69
    Hi, how are you progressing on the new version? Is it realistic that we will see a release this month (March)? Thanks
    Raja Nadar
    @rajanadar
    @daborg69 the 0.9.x version took a hit in terms of its timeline (due to some business travel etc). I am re-adjusting it this week, and aiming for a mid-april first release. Also changing the release method a bit.
    David Cumps
    @CumpsD
    looking forward to the 0.9.x version :) using the deprecated way of accessing mssql now in vault, which works ofcourse, but for how long :p
    andrewhart098
    @andrewhart098
    hello
    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
    andrewhart098
    @andrewhart098
    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
    andrewhart098
    @andrewhart098
    Hi @rajanadar - is there anything I can do to help with the 0.10 release?
    kiranvengala
    @DotNetGeek2017_gitlab
    There is no support for .net core 1.0
    Raja Nadar
    @rajanadar
    Yes. I am working on that next. Enhance the next NuGet package with multi platform outputs.
    kiranvengala
    @DotNetGeek2017_gitlab
    Where do we find the vault client api spec??
    i was going through the https://www.vaultproject.io/ i do not see any
    Raja Nadar
    @rajanadar
    @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.
    Raja Nadar
    @rajanadar
    also, the vault api spec is here: https://www.vaultproject.io/api/index.html
    the vaultsharp docs is here (more to be added) https://github.com/rajanadar/VaultSharp/blob/master/README.md
    --
    Raja Nadar
    @rajanadar
    @/all VaultSharp 0.10.4002 is now available. On par with Vault 0.10.4

    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.

    --
    @DotNetGeek2017_gitlab The latest release supports .Net Core 1.0.
    Rodrigo Vidal
    @rodrigovidal
    @rajanadar Hi I'm trying to use VaultSharp with AWS IAM Auth. Do you have an example on how to use IAMAWSAuthMethodInfo?
    do I have to sign the request by myself?
    leowmjw
    @leowmjw
    @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?
    Raja Nadar
    @rajanadar
    @rodrigovidal yes, you need to sign the request yourself. Let me know details, and if it is something generic, i'll bake it in in the coming days.
    @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.
    Raja Nadar
    @rajanadar
    In short,
    1. When you initialize the Vault Client, nothing really happens. No login is performed.
    1. When the first Vault API call is requested, the login call happens and the token is stored in the library.
    1. For further API calls, NO relogin happens. The previous token is used.
    This Auth Info is available in the IAuthMethodInfo object after step 2.

    leowmjw
    @leowmjw
    Thanks for the clarification @rajanadar ! I'll do a PR documenting this case and as an example.
    simonthum
    @simonthum
    Hi @rajanadar ,
    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?