Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: Add interoperability matrix #5478

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from
+42 −1
Draft

docs: Add interoperability matrix #5478

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
145ce03
docs: Add interoperability matrix
Dan-Heath Jan 27, 2025
e2db6fd
docs: Remove one table version
Dan-Heath Jan 29, 2025
ee7d8f0
docs: New format
Dan-Heath Jan 29, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
35 changes: 35 additions & 0 deletions website/content/docs/configuration/target-aliases/interoperability-matrix.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,35 @@
---
layout: docs
page_title: Transparent sessions interoperability matrix
description: >-
Refer to a matrix to determine which partner products and applications are supported by the Boundary components required for transparent sessions.
---

# Transparent sessions interoperability matrix

Transparent sessions require you to use the Boundary installer to install the Boundary Client Agent.
To support a variety of use cases, Boundary verifies implementation and integrations with partner products and applications.

Refer to the table to determine which products have been tested for use with specific versions of the installer and Client Agent.

| Product | Verified Boundary installer versions | Verified Client Agent versions | Notes |
|----------------|---------------------------|----------------------------|---------------|
| Cloudflare WARP client | 0.1.1 | 0.1.1 | Refer to [compatibility issue](/boundary/docs/api-clients/client-agent#cloudflare-warp-client)
| Crowdstrike Falcon | 0.1.1 | N/A |
| SentinelOne Singularity | 0.1.1 | 0.1.1 |
| ZeroTier | 0.1.1 | 0.1.1 |
| Huntress EDR client | 0.1.1 | 0.1.1| Refer to [compatibility issue](/boundary/docs/api-clients/client-agent#huntress-edr-client)
| OpenVPN | 0.1.1 | 0.1.1 |
| Tailscale | 0.1.1 | 0.1.1 |
| WireGuard | 0.1.1 | 0.1.1 |

| Product | Version | Verified Boundary installer versions | Verified Client Agent versions | OS versions | Additional information
|---------|---------|--------------------------------------|--------------------------------|-------------|------------|
| Cloudflare WARP client | 2024.12.554.0 | 0.1.1 | 0.1.1 | Windows 11 Pro (Version 24H2), MacOS Sonoma 14.6 | Refer to [compatibility issue](/boundary/docs/api-clients/client-agent#cloudflare-warp-client)

## More information

For more information, refer to the following topics:

- [Configure transparent sessions](/boundary/docs/configuration/target-aliases/transparent-sessions)
- [Boundary Client Agent](/boundary/docs/api-clients/client-agent)
4 changes: 3 additions & 1 deletion website/content/docs/configuration/target-aliases/transparent-sessions.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,6 +34,8 @@ Make sure to select the options **Boundary Client Agent**, **CLI**, and **Deskto
$ boundary client-agent status
```

Refer to the [transparent sessions interoperability matrix](/boundary/docs/configuration/target-aliases/interoperability-matrix) for a list of the third-party products that are compatible with the Boundary installer and Client Agent.

## Configure targets

The following section details how to configure targets and test the transparent sessions public beta feature.
Expand All @@ -43,7 +45,7 @@ The following section details how to configure targets and test the transparent
If you use a cluster that was created earlier than release 0.16.0, you must add the grant `list-resolvable-aliases` so that the client agent can populate the local alias cache.

As an example, you could add the grant:

`type=user;actions=list-resolvable-aliases;ids=*`.

</Tip>
Expand Down
4 changes: 4 additions & 0 deletions website/data/docs-nav-data.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -614,6 +614,10 @@
"color": "neutral"
},
"path": "configuration/target-aliases/transparent-sessions"
},
{
"title": "Transparent sessions interoperability matrix",
"path": "configuration/target-aliases/interoperability-matrix"
}
]
},
Expand Down