Skip to content
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.

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

Added new OpenSSH break glass admin management operations guide #49804

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

deusxanima
Copy link
Contributor

Added guide with instructions on how to configure OpenSSH break glass access with Teleport CA signed certificates for out-of-band access if Teleport server resources or cluster servers become unavailable and/or unresponsive.

Copy link

github-actions bot commented Dec 5, 2024

🤖 Vercel preview here: https://docs-5h5xxnof7-goteleport.vercel.app/docs

Run the following after logging into Teleport via `tsh login` as the impersonating user:

```bash
tctl auth sign --ttl 24h --user=breakglass --out=/safe/path/breakglass --format openssh
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This user certificate is (or, at least, I really hope is) issued by the user CA, which is the signer that signs all the user certs that are given out to users, but above we configured opensshd to trust the openssh CA, which signs certificates that are only ever in possession of the proxy - a regular user won't be able to obtain such a certificate.

Copy link
Contributor Author

@deusxanima deusxanima Dec 6, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Interesting. From what I can see, it looks like the CA that's exported with the proxy via the https://proxy.example.com/webapi/auth/export?type=openssh endpoint, is of type "user" instead of OpenSSH according to the extension appended at the end:
e.g.:

cert-authority ssh-rsa <my_ca> clustername=alen.teleport.sh&type=user

I can confirm that passing type=user instead during the export produces a different CA, but if the former is not expected to work with user certs generated via tctl auth sign ... --format openssh, there may be another problem altogether as I can get it to work reliably right now (unless again I'm turned around on this and misunderstanding, which very likely could be the case)

Copy link
Contributor

@webvictim webvictim left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Comments

@ptgott
Copy link
Contributor

ptgott commented Dec 18, 2024

Hi @deusxanima, would this PR address #3760? It's one of our oldest docs issues, so it'd be great to see it cleared!

@deusxanima
Copy link
Contributor Author

Hi @deusxanima, would this PR address #3760? It's one of our oldest docs issues, so it'd be great to see it cleared!

Partially, yes. Specifically it would cover the "If Teleport Auth cluster is offline" scenario in the original request.

Copy link

github-actions bot commented Jan 8, 2025

Amplify deployment status

Branch Commit Job ID Status Preview Updated (UTC)
alen/breakglass_access 8dc939a 2 ❌FAILED alen-breakglass-access 2025-01-08 20:50:22

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants