Heath Stewart
Heath Stewart
There are no new suppressions in this PR. I'll open a tracking issue for this, but it should not block the PR.
As @christothes brought up in triage, perhaps this could be broken up into bite-sized issues - some of which could be done in MQ potentially.
Could we go even further given rust's generally actionable error messages, pointing to further information if needed? The crux of the issues with `default-features` is, of course, that they are...
This is a service error response: ``` { "error": { "code": "BadParameter", "message": "Unable to parse X5c certificate chain and locate leaf certificate" } } ``` @jlichwa can someone from...
The API version is different. The only other thing I can think of is that `Az.KeyVault` is handling the binary data for `x5c` wrong. There was a case they were...
While that's almost the right base (those bytes from the file aren't base64-encoded, so that local variable name is misleading), I just reread the original issue and I'm confused. It...
In what format is the public key? PEM? DER?
Any reason to think a self-signed cert wouldn't work in reproducing this? /cc @nisha-bhatia
You should always pass raw bytes to the SDK - don't encode anything yourself. That's what the SDK will do as needed. We don't base64-encode PEM files since the service...
The SDK expects raw bytes. It sends whatever you pass to the service. If the service doesn't support PEM, then you have to extract the sections. The SDKs are most...