Empty sync

[JoskaM86]

Sync creates empty group named according to keepass entry for vault and sysdate.

Is there a way how to find out, what's wrong in sync? Possibly it can be the format of value in the path field. I've used

\first_vault_node\

[osminm]

Having the same issue on a windows 10/keepass 2.47, empty group. The plugin menu option didn't show up when trying from a Mac/KeePassX 2.0.3 and hoped windows would work. Looked through the code and I can't see where the login URL is put together fully, e.g. https://localhost:8200/v1/auth/ldap/login/myusername. Line 149 only shows of SynchronousVaultClient.cs shows "authPath + "/login/" + user sent to loginRequest. The function loginRequest doesn't show how this URL path is put together either "https://localhost:8200/v1/auth/l".

[Karreg]

Hello,

Unfortunately, KeePass is not friendly for displaying issues from a plugin. It's hard to say what's happening.
I'll try to work on this today.

[Karreg]

A new version has been released, with a log windows shown on synchronization to help understand what happens. Let me know if that helps.

[osminm]

The log window is helpful..it complains about missing Newtonsoft.Json. I see that dll in C:\Users\user\AppData\Local\KeePass\PluginCache\WnysolFW6S6layDubVWM but version is not what it doesn't match what it shows below.

Found vault entry vault-test
Exception for kv: Could not load file or assembly 'Newtonsoft.Json, Version=10.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed' or one of its dependencies. The system cannot find the file specified.
at Vault.VaultHttpClient.JsonSerialize[T](T content)
at Vault.VaultHttpClient.Put[TI,TO](Uri uri, TI content, String vaultToken, TimeSpan wrapTtl, CancellationToken ct)
at Vault.VaultClient.Put[TI,TO](String path, TI content, TimeSpan wrapTtl, CancellationToken ct)
at Vault.Endpoints.Endpoint.Write[TParameters,TData](String path, TParameters data, CancellationToken ct)
at VaultSyncPlugin.SynchronousVaultClient.d__e.MoveNext()
Secrets fetched, will now inject them in the database
Done.

[Karreg]

That's weird. The Newtonsoft JSON.NET dll should be included in the plgx file. There must be some mistmactch, and that may be related to my computer setup. I'll have a look at that.

[Karreg]

Found it. Vault.net requires JSON.NET 10 when I reference JSON.NET 12.
I'll try to bind the reference to use the latest JSON.NET version. If that causes issues, I will downgrade the JSON.NET version I use...

[Karreg]

Can you try with this version?

(Removed)

[Karreg]

Don't. it comes with some test code I left aside to manage JSON secrets... I'll give your another version soon :)

[Karreg]

Here is a version with JSON.NET 10 since keepass does not handle binding redirect. Tell me how it's going for you.

VaultSyncPlugin.zip

[osminm]

Looking better but seems I'm now dealing with a local issue..the process hangs after displaying a "Found vault entry.." message. I tested accessing the URL and noticed it launches fine from keepass with chrome & firefox, however it does not open with IE (2019 server ver 1809 via RDP). I'm on a Mac so will try spinning up a Windows 10 VM and test there instead.

[Karreg]

The plugin is not intended to work with keepassx. I'm not even sure it's working fine on linux with mono...

[osminm]

FYI, looks like I'm dealing with a TLS/IE issue since vault is behind a CA issued SSL cert. It showed this error:
Found vault entry vault-test
Exception for kv: One or more errors occurred.
at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification)
at VaultSyncPlugin.SynchronousVaultClient.d__e.MoveNext()
Secrets fetched, will now inject them in the database
Done.

I'm going to test next with a development vault non-ssl instance on my machine..expect that will work fine.

[Karreg]

It's hard to tell, this exception is an asynchronous exception, the real exception is hidden. I'll try to find where this is executed, and try to display the real exception instead.

[Karreg]

This should be an issue with authentication. There is not SSL validation since I have the same issue (see here)

Can you try with this version? I have added logs on authentication.

VaultSyncPlugin.zip

[osminm]

FYI, corrected the crypto issues in our config (it was affecting another tool). used the zip you shared above and getting to this point. Question, in your instructions you suggest using 'username' for basic auth. I used the name I gave the basic auth engine, defaults to userpass:

With SSL:
Found vault entry vault-test
Trying to authenticate to https://vault:8200//userpass/login/ with user xxx
Authenticated with token s.05Q28xxx...

Without SSL:
Found vault entry vault-test
Trying to authenticate to https://vault:8200//userpass/login/ with user xx
Authenticated with token s.05Q28VLxxx...
Found vault entry vault-test
Trying to authenticate to http://vault:8200//userpass/login/ with user xxx
Error on authentication: Unexpected response, status code BadRequest
at Vault.VaultHttpClient.d__14.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Vault.VaultHttpClient.d__131.MoveNext() Exception for kv: Unexpected response, status code BadRequest at Vault.VaultHttpClient.<HttpRequest>d__14.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Vault.VaultHttpClient.<HttpRequest>d__131.MoveNext()
Secrets fetched, will now inject them in the database
Done.