-
#### Feature Description
1. Nomad terminates tls connections via spiffe/go-sdk, which in turn provisions and atomically cycles cryptographic material on `crypto/tls.Config`.
2. Nomad further uses s…
-
#### Feature Description
1. Vault terminates tls connections via spiffe/go-sdk, which in turn provisions and atomically cycles cryptographic material on `crypto/tls.Config`.
2. Vault further uses s…
-
### Use-cases
Provider developers across the ecosystem will have some common use cases they will want to research documentation on how to accomplish their goals. For example, how to implement provi…
bflad updated
4 months ago
-
https://github.com/hashicorp/boundary/blob/48e4fcce252c16f95cf3813c9f231e3f1e22e802/internal/cmd/commands/connect/rdp.go#L61
*boundary rdp* uses "open rdp://" as command to open rdp client on Mac…
-
**Is your feature request related to a problem? Please describe.**
I'm not sure if this feature is in place or not, but I didn't find it from the docs.
When creating a target, there's a default po…
-
Using PEM files for accessing droplets is not best practice.
Vault should be enabled as a CA that can issue short-lived certificates which can be used to access droplets.
HashiCorp Boundary could …
-
We run our vault instance in AKS and want to use the new [Azure Workload Identity](https://learn.microsoft.com/en-us/azure/aks/workload-identity-overview) service to authenticate against Azure resour…
-
Sometimes this message appears (no idea what it means)
```
Error when querying all channel values:
internal error in pointer analysis: node has no enclosing object (please report this bug)
```
-
_This issue was originally opened by @dylanmtaylor in https://github.com/hashicorp/packer/issues/11820 and has been migrated to this repository. The original issue description is below._
---
#### Des…
-
#### Feature Description
1. Consul terminates tls connections via spiffe/go-sdk, which in turn provisions and atomically cycles cryptographic material on `crypto/tls.Config`.
2. Consul further uses …