Viewing profile — jefferai

Boundary will indeed give you a bearer token after authentication to present to take further actions in its API. So you'd authenticate to Boundary, get a bearer token, and use that…

TCP targets (the only kind currently in Boundary) actually work with _any_ TCP connection. The `boundary connect ` bits are just some CLI syntactic sugar around the main `boundary …

We don't have something natively, but you can control the address via BOUNDARY_ADDR env var or the -addr flag per-call, and you can use -token-name with the CLI to switch between n…

Without committing to any specifics, I'll say that we are very aware of use-cases where a daemon on the end host can provide enhanced benefits. As you can imagine we did quite a bi…

In an immediate sense you could have targets point to services handled by Connect, so you'd have client -> Boundary worker -> local Connect entrypoint -> end service. We'll be look…

Check out https://www.boundaryproject.io/docs/concepts/security/connec... for lots of details!

Generally speaking this is designed for accessing your own systems, not the systems of a third party being consumed as a SaaS. That said, any such provider that allows you to restr…

By "direct network access" we mean between the client and the end host. The Boundary worker node (which proxies traffic) would need to be able to make a network connection to the e…

As you say, it's a big question. But one way to start is by integrating this _within your VPN_ such that network access + credentials alone are not enough. With Boundary you could …

You can use Consul-Template ( https://github.com/hashicorp/consul-template ) -- yes, it really needs a rename -- to do this with Vault (or Consul).

S3 is one of the available storage backends. You only need consul/etcd/zookeeper if you want to have a high availability setup.

You didn't. Mirroring in this case refers to using git --mirror. You're assuming it works like a traditional file system or block level mirror, but it doesn't. Corruption would in …