Closed tomachristian closed 23 hours ago
Hi @tomachristian , thank you for giving Lowkey Vault a try and thank you for reporting this issue! As I have seen, you are right, the official .Net client does not appear to implement the official HTTP API in a case-sensitive manner.
I will take a look, find all other cases where this might be an issue and fix them together as soon as possible.
Thank you! Awesome work on this project! Really appreciate it!
Thank you for your feedback! I am glad it is useful! Fix this issue, please try it with v2.5.6 and let me know whether it solved your problem!
Thank you in advance!
I can confirm that the latest version no longer has the problem. Thank you!
Thank you!
Describe the bug
Using the official KeyVault .NET library for working with LowKey Vault, I noticed that the
unwrapKey
andwrapKey
endpoints were not working with the library. Investigating this further I noticed that Lowkey Vault is using lower-case paths for its controller mappings... and that they are case-sensitive, so the requests from the official .NET library do not work, because those useunwrapKey
instead ofunwrapkey
.Workaround
For anyone still wanting to use this, you can create a
DelegatingHandler
that you place in the processing pipeline that will lowercase the path that the .NET official library uses. You can get the gist of it from hereThis will not work for all endpoints, you need to tailor the workaround for your own needs.