Skip to content

Commit 8674af5

Browse files
committed
update browser rendering overview
1 parent dd2ec40 commit 8674af5

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

src/content/docs/cloudflare-one/applications/non-http/browser-rendering.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ sidebar:
55
order: 3
66
---
77

8-
Cloudflare can render SSH, VNC, and RDP applications in a browser without the need for client software or end-user configuration changes.
8+
Cloudflare can render SSH, VNC, and RDP applications in a browser without the need for client software or end-user configuration changes. For SSH and VNC, user email prefixes must match their username on the server. RDP leverages your existing Windows username and passwords for authenticating to the Windows server; Cloudflare does not manage any credentials on the Windows server.
99

1010
## Limitations
1111

src/content/docs/cloudflare-one/applications/non-http/index.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -23,11 +23,11 @@ If you would like to define how users access specific infrastructure servers wit
2323

2424
## Clientless access
2525

26-
Clientless access methods are suited for organizations that cannot deploy the WARP client or need to support third-party contractors where installing a client is not possible. Clientless access requires onboarding a domain to Cloudflare and configuring a public hostname in order to make the server reachable. Command logging is not supported, and user email prefixes must match their username on the server.
26+
Clientless access methods are suited for organizations that cannot deploy the WARP client or need to support third-party contractors where installing a client is not possible. Clientless access requires onboarding a domain to Cloudflare and configuring a public hostname in order to make the server reachable. Command logging is not supported.
2727

2828
### Browser-rendered terminal
2929

30-
Cloudflare's [browser-based terminal](/cloudflare-one/applications/non-http/browser-rendering/) allows users to connect over SSH and VNC without any configuration. When users visit the public hostname URL (for example, `https://ssh.example.com`) and log in with their Access credentials, Cloudflare will render a terminal in their browser.
30+
Cloudflare's [browser-based terminal](/cloudflare-one/applications/non-http/browser-rendering/) allows users to connect over SSH, RDP, and VNC without any configuration. When users visit the public hostname URL (for example, `https://ssh.example.com`) and log in with their Access credentials, Cloudflare will render a terminal in their browser. For RDP connections, users must authenticate to the Windows server using their Windows username and password in addition to being authenticated by Cloudflare Access.
3131

3232
### Client-side cloudflared (legacy)
3333

0 commit comments

Comments
 (0)