Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[FEATURE REQ] Retrieve certificate with private key using Azure.Security.KeyVault.Certificates.CertificateClient / KeyVaultCertificate
See original GitHub issueLibrary or service name.
Azure.Security.KeyVault.Certificates
Is your feature request related to a problem? Please describe.
KeyVaultCertificate only exposes the public key, and for the private key the Azure.Security.KeyVault.Secrets must be used, where a x509certificate2 must be manually constructed from the byte array.
It would be more convenient to have the option to use the CertificateClient to get a x509certificate2 directly. It would also be more consistent with the import API, which does mandate the private key to reside in the cert. So if I upload the private key, it makes sense for me to be able to download it - if I drew an analogy to secrets, it would be having to use one library to create a secret and another library to retrieve it…
Issue Analytics
- State:
- Created 3 years ago
- Reactions:6
- Comments:11 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Our preview out now includes APIs for parsing the URI.
The
ParseSecretNamemethod in your sample should be part of the library, IMO.In the UI, or the CLI, everything I touch is a certificate. But in code, I need to get a secret?
And, the Secrets SDK requires a string, but the certificate SDK gives me a URI (?!?)
I’m sure there is a good reason that the certificate points to a specific secret version/instance using a URI. How about an overload in the Secrets API that accepts a URI? Making the consumer find this thread/sample to put the pieces together is sub-optimal.