Telnet Access Management

Legacy devices still need Telnet, but open ports are indefensible. OnePAM bridges browser terminals to legacy infrastructure with SSO and MFA.

Zero Trust for Legacy Infrastructure

Browser-based Telnet via WebSocket (xterm.js)
Full session recording in asciinema v2 format
Telnet option negotiation (WILL/WONT/DO/DONT)
NAWS terminal size negotiation
TLS upgrade support (STARTTLS / Telnet over TLS on port 992)
Terminal type negotiation for device compatibility
Identity-verified access with SSO and MFA
Zero Trust access to legacy infrastructure

Browser Telnet Session

onepam — telnet Connecting to switch-core-01:23 via OnePAM... Identity verified: bob@acme.co (NetOps) Session recording started (ID: ses_tel_4f8n) Negotiating: NAWS, TTYPE... done switch-core-01> show interfaces brief Interface Status Speed Description Eth1/1 up 10G Uplink-Core Eth1/2 up 10G Server-Rack-A Eth1/3 down 1G Mgmt-OOB switch-core-01> TELNET GATEWAY WebSocket → Telnet bridge • IAC negotiation (NAWS, TTYPE) • Session recording (asciinema v2) • TLS upgrade Legacy devices, mainframes, industrial systems — all secured with Zero Trust access and full audit trails

Three Steps to Secure Access

1. Sign Up With SSO

Connect your identity provider — Okta, Azure AD, Google Workspace, or any SAML/OIDC provider. Your team logs in with existing credentials.

2. Add Your Resources

Register servers, databases, Kubernetes clusters, and web apps. Define who can access what with role-based policies.

3. Access Securely

Your team accesses resources through the browser — identity-verified, session-recorded, and audit-logged. No VPN, no exposed ports.

Try Telnet Access Management — Free for 14 Days

From signup to your first secure session in under 5 minutes. No infrastructure changes, no credit card, no sales call.