Replies: 2 comments
-
Answering myself... the endpoint expects an authentication in the header that is missing. |
Beta Was this translation helpful? Give feedback.
-
Hi @garca7 , You are right about the missing header, adding it should do the trick. Regarding the certificates, I would suggest to please check out these wiki pages: Also, please make sure to check these example repositories showing how to use Lowkey Vault with the official Azure clients including the certificate configs: https://github.com/nagyesta/lowkey-vault/wiki/Example:-How-can-you-use-Lowkey-Vault-in-your-tests#examples Also, checked the
Please let me know in case further assistance is needed! Best of luck! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
(edited to correct port numbers and response)
Hello, KeyVault newbie here. I'm struggling getting the lowkeyvault container to accept secrets. The following post
PUT https://localhost:8443/secrets/XXXXXXXXXXX?api-version=7.4
Content-Type: application/json
Accept: application/json
{
"value":"YYYYYYY",
"attributes":{}
}
fails with a
HTTP/1.1 401
WWW-Authenticate: Bearer resource="https://localhost:8443", authorization_uri="https://localhost:8443/secrets/9e6bf9471a94be5460c98164b080fe694df72caba57aee05b3b589605d955584"
Content-Length: 0
Date: Mon, 23 Sep 2024 12:19:59 GMT
Response code: 401; Time: 136ms (136 ms); Content length: 0 bytes (0 B)
What not seems reasonable, is that the endpoint https://localhost:8443/api/swagger-ui/swagger-ui/index.html is not showing any /secrets entry, which likely is the source of the problem.
I'm starting the container with these arguments (BTW, in spite of the LOWKEY_DEBUG_REQUEST_LOG setting, I don't have any detailed traces in the container logs):
Any ideas?
Beta Was this translation helpful? Give feedback.
All reactions