-
**What steps did you take and what happened:**
I’ve created a certificate with App Service Certificate. This one is stored as a secret in a keyvault (PFX with cert and key embedded) in base64. It’s…
deuch updated
4 weeks ago
-
-
### Is there an existing issue for this?
- [X] I have searched the existing issues
### Community Note
* Please vote on this issue by adding a :thumbsup: [reaction](https://blog.github.com/2016-…
-
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help…
-
**"DP-5: Use customer-managed key option in data at rest encryption when required"** states Data at Rest Encryption Using CMK is supported, which is not accurate, as Key Vault is encrypted using platf…
-
### Is there an existing issue for this?
- [X] I have searched the existing issues
### Community Note
* Please vote on this issue by adding a :thumbsup: [reaction](https://blog.github.com/2016-…
-
Our scenario tests are currently relying on a personal GitHub PAT token for GitHub operations, such as clean-up.
We should replace it with a bot PAT token that is managed by secret manager.
-
**Is your feature request related to a problem? Please describe.**
When using ci/cd pipeline that has federated credentials we are forced to fall back to using client id and secret when using…
-
### Is there an existing issue for this?
- [X] I have searched the existing issues
### Community Note
* Please vote on this issue by adding a :thumbsup: [reaction](https://blog.github.com…
-
The problem appears to be that my key vault's access policies are not being used. For example, in this case, I have access to use a particular key for encryption; however, the error says that such an …