Skip to content

[ZT] Infra Access legacy notes #18424

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

Merged
merged 1 commit into from
Nov 26, 2024
Merged

[ZT] Infra Access legacy notes #18424

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
8 changes: 3 additions & 5 deletions ...t/docs/cloudflare-one/applications/non-http/short-lived-certificates-legacy.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,15 +3,13 @@ title: Short-lived certificates (legacy)
pcx_content_type: how-to
sidebar:
order: 6
head:
- tag: title
content: Configure short-lived certificates (legacy)
label: Short-lived certificates (legacy)
---

import { Render } from "~/components";

:::note[Short-lived certificates are now managed through Access for Infrastructure.]
Cloudflare recommends configuring short-lived certificates through our new [Access for Infrastructure](/cloudflare-one/connections/connect-networks/use-cases/ssh/ssh-infrastructure-access/) workflow. Access for Infrastructure supports differing SSH aliases out-of-the-box, removes the need for client SSH configuration, and allows for more granular security policies.
:::note
Not recommended for new deployments. We recommend using [Access for Infrastructure](/cloudflare-one/connections/connect-networks/use-cases/ssh/ssh-infrastructure-access/) to configure short-lived certificates for SSH.
:::

<Render
Expand Down
2 changes: 1 addition & 1 deletion ...e/connections/connect-networks/use-cases/ssh/ssh-cloudflared-authentication.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ pcx_content_type: how-to
title: Connect to SSH with client-side cloudflared (legacy)
sidebar:
order: 5
label: SSH with client-side cloudflared
label: SSH with client-side cloudflared (legacy)
---

import { Render } from "~/components";
Expand Down
5 changes: 3 additions & 2 deletions src/content/docs/cloudflare-one/policies/gateway/network-policies/ssh-logging.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,14 +1,15 @@
---
title: SSH proxy and command logs
title: SSH proxy and command logs (legacy)
pcx_content_type: how-to
sidebar:
order: 3
label: SSH proxy and command logs (legacy)
---

import { Render } from "~/components";

:::note
Cloudflare recommends configuring SSH command logs through our new [Access for Infrastructure](/cloudflare-one/connections/connect-networks/use-cases/ssh/ssh-infrastructure-access/) workflow. Access for Infrastructure supports differing SSH aliases out-of-the-box, custom SSH ports, and Logpush integrations.
Not recommended for new deployments. We recommend using [Access for Infrastructure](/cloudflare-one/connections/connect-networks/use-cases/ssh/ssh-infrastructure-access/) to manage SSH sessions and log SSH commands.
:::

Cloudflare Zero Trust supports SSH proxying and command logging using Secure Web Gateway and the WARP client.
Expand Down