-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem importing a certificate #1283
Comments
Hi @Courela , I am very bad at .Net, but I guess it might be an SDK bug, because the duplicate The methods in question might be these: The Containing Then the Do you need this import to happen because that is the workload you need to test, or is it part of the test setup? If it is the test setup, then you may want to consider loading the vault contents at startup as a workaround while the SDK bug is being fixed. Thank you! |
Thank you for the investigation! I agree, it should be because of that method call with "/" as parameter, when |
Thank you and best of luck! Please let me know in case there is anything I can do on Lowkey Vault side! |
I opened a bug on Azure SDK forum |
That's really it, I managed to compile the source code without the end slash on |
Great news, I am glad it is confirmed! |
And now it fails when I try to create a self-signed certificate... The slash needs to be in |
Question
Hello,
I'm using Azure SDK to import a certificate to KeyVault. I'm using a method called
Azure.Security.KeyVault.Certificates.ImportCertificate
which translates into a call to an endpoint
/certificates/{certificateName}/import
as I can see in this Lowkey-Vault file (using V7_3)
https://github.com/nagyesta/lowkey-vault/blob/main/lowkey-vault-app/src/main/java/com/github/nagyesta/lowkeyvault/controller/v7_3/CertificateController.java#L50
The problem is that Lowkey-Vault says that the endpoint being called is
/certificates//someIdpName/import?api-version=7.3
I don't know why the endpoint has two slashes in between
/certificates
andsomeIdpName/import
...Is this something you can help me with? Do you know where that extra slash is coming from? Maybe this is a question to be asked in Azure SDK forum...
Thanks in advance.
The text was updated successfully, but these errors were encountered: