<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/using-rbac-with-openssh-servers-7vrjqstsi" -->

---
title: Using RBAC with OpenSSH servers | daily.dev
description: A walkthrough explains how to restrict SSH access to critical Teleport auth/proxy servers when the rest of an infrastructure runs plain OpenSSH, which lacks...
canonical: https://daily.dev/posts/using-rbac-with-openssh-servers-7vrjqstsi
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Using RBAC with OpenSSH servers | daily.dev
og:description: A walkthrough explains how to restrict SSH access to critical Teleport auth/proxy servers when the rest of an infrastructure runs plain OpenSSH, which lacks...
og:url: https://daily.dev/posts/using-rbac-with-openssh-servers-7vrjqstsi
og:image: https://api.daily.dev/og/posts/7vrJQstsi.png
og:image:alt: Using RBAC with OpenSSH servers
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Using RBAC with OpenSSH servers

**[Teleport](https://daily.dev/sources/teleport)** · 4 min read · 0 upvotes · 0 comments

## Summary

A walkthrough explains how to restrict SSH access to critical Teleport auth/proxy servers when the rest of an infrastructure runs plain OpenSSH, which lacks native label support for Teleport's RBAC. The approach labels Teleport's own auth/proxy nodes and defines an admin role with full access alongside a 'dev' role that denies access to nodes labeled role=teleport, using YAML role definitions and OpenSSH principal restrictions. It concludes that full RBAC requires deploying Teleport's own SSH daemon instead of relying on sshd.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://goteleport.com/blog/rbac-with-openssh>

## Questions this post answers

### How can I restrict SSH access to specific servers when using Teleport alongside plain OpenSSH nodes?

Label the Teleport auth and proxy servers (for example role=teleport in teleport.yaml) and define role-based access rules: an admin role with node_labels set to wildcard access, and a dev role with a deny rule blocking node_labels role=teleport while allowing access to all other nodes. This restricts non-admin users from SSHing into Teleport's auth/proxy servers while leaving full access to plain OpenSSH nodes.

_daily.dev surfaces practical RBAC and access-control patterns for engineers securing mixed SSH environments._

### Why is it hard to build RBAC on top of traditional key-based SSH authentication?

Key-based SSH authentication makes RBAC difficult because keys don't expire on their own, so there's no natural point to re-apply access rules. SSH certificates solve this since they automatically expire and require re-issuance, creating a convenient checkpoint for enforcing role-based access policies each time a certificate is renewed.

_Engineers weighing SSH key management versus certificate-based auth can track these tradeoffs on daily.dev._

## Similar posts on daily.dev

- [Stop managing SSH keys on every server and switch to Teleport](https://daily.dev/posts/stop-managing-ssh-keys-on-every-server-and-switch-to-teleport-zoja48gov) · All Things Open · 0 upvotes · 0 comments

---

Tags: [#ssh](https://daily.dev/tags/ssh)

[View this post on daily.dev](https://daily.dev/posts/using-rbac-with-openssh-servers-7vrjqstsi)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Using RBAC with OpenSSH servers","url":"https://daily.dev/posts/using-rbac-with-openssh-servers-7vrjqstsi","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/using-rbac-with-openssh-servers-7vrjqstsi"},"datePublished":"2026-08-23T12:23:28.849Z","dateModified":"2026-08-23T12:56:18.658Z","description":"A walkthrough explains how to restrict SSH access to critical Teleport auth/proxy servers when the rest of an infrastructure runs plain OpenSSH, which lacks...","image":"https://media.daily.dev/image/upload/s--CxzD6vbw--/f_auto/v1722860399/public/Placeholder%2005","thumbnailUrl":"https://media.daily.dev/image/upload/s--CxzD6vbw--/f_auto/v1722860399/public/Placeholder%2005","isAccessibleForFree":true,"articleSection":"Teleport","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Teleport","logo":"https://media.daily.dev/image/upload/s--Dw-Bbw6O--/c_limit,w_256/f_auto,q_auto/v1787487494/logos/teleport?_a=BAMAMicg0","url":"https://daily.dev/sources/teleport"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/using-rbac-with-openssh-servers-7vrjqstsi","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"ssh","timeRequired":"PT4M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Teleport","item":"https://daily.dev/sources/teleport"},{"@type":"ListItem","position":3,"name":"Using RBAC with OpenSSH servers"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/using-rbac-with-openssh-servers-7vrjqstsi#faq","mainEntity":[{"@type":"Question","name":"How can I restrict SSH access to specific servers when using Teleport alongside plain OpenSSH nodes?","acceptedAnswer":{"@type":"Answer","text":"Label the Teleport auth and proxy servers (for example role=teleport in teleport.yaml) and define role-based access rules: an admin role with node_labels set to wildcard access, and a dev role with a deny rule blocking node_labels role=teleport while allowing access to all other nodes. This restricts non-admin users from SSHing into Teleport's auth/proxy servers while leaving full access to plain OpenSSH nodes. daily.dev surfaces practical RBAC and access-control patterns for engineers securing mixed SSH environments."}},{"@type":"Question","name":"Why is it hard to build RBAC on top of traditional key-based SSH authentication?","acceptedAnswer":{"@type":"Answer","text":"Key-based SSH authentication makes RBAC difficult because keys don't expire on their own, so there's no natural point to re-apply access rules. SSH certificates solve this since they automatically expire and require re-issuance, creating a convenient checkpoint for enforcing role-based access policies each time a certificate is renewed. Engineers weighing SSH key management versus certificate-based auth can track these tradeoffs on daily.dev."}}]}
```

