Skip to content

[ZT] SSH IdP alias option #18282

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] SSH IdP alias option #18282

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
2 changes: 1 addition & 1 deletion ...re-one/connections/connect-networks/use-cases/ssh/ssh-infrastructure-access.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -79,7 +79,7 @@ ssh <username>@<target IP>

SSH with Access for Infrastructure also supports `scp` and `rsync` commands. At this time, `sftp` is not supported.

For more information, refer to the [Access for Infrastructure documentation](/cloudflare-one/applications/non-http/infrastructure-apps/#connect-as-a-user).
To learn more about user connections, refer to the [Access for Infrastructure documentation](/cloudflare-one/applications/non-http/infrastructure-apps/#4-connect-as-a-user).

## SSH command logs

Expand Down
8 changes: 7 additions & 1 deletion src/content/partials/cloudflare-one/access/add-infrastructure-app.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,13 @@ import { Tabs, TabItem, Render } from "~/components"
9. To secure your targets, configure a policy that defines who can connect and how they can connect:
1. Enter any name for your policy.
2. Create a rule that matches the users who are allowed to reach the targets. For more information, refer to [Access policies](/cloudflare-one/policies/access/) and review the list of [infrastructure policy selectors](/cloudflare-one/applications/non-http/infrastructure-apps/#infrastructure-policy-selectors).
3. In **Connection context**, enter the UNIX usernames that users can log in as (for example, `root` or `ec2-user`).
3. In **Connection context**, configure the following settings:
- **SSH user**: Enter the UNIX usernames that users can log in as (for example, `root` or `ec2-user`).
- **Allow users to log in as their email alias**: (Optional) When selected, users who match your policy definition will be able to access the target using their email address prefix. For example, `[email protected]` could log in as `jdoe`.

:::note
Cloudflare will not create new users on the target. UNIX users must already be present on the server.
:::
4. Select **Add application**.
</TabItem>
<TabItem label="API">
Expand Down
Loading