Add docs for hardware keys in Connect #48453
Conversation
gzdunek
added
no-changelog
|
This pull request is automatically being deployed by Amplify Hosting (learn more). |
|
🤖 Vercel preview here: https://docs-8akef1qt1-goteleport.vercel.app/docs/ver/preview |
|
🤖 Vercel preview here: https://docs-c57x6jhnu-goteleport.vercel.app/docs/ver/preview |
github-actions
bot
requested review from
mmcallister,
ptgott,
r0mant,
xinding33 and
zmb3
| @@ -216,6 +216,27 @@ The application connection tab shows an example command that can be used to quer | |||
| Requests sent under the displayed address will be proxied through an authenticated tunnel to the | |||
| application. | |||
|
|
|||
| ## Hardware key support | |||
There was a problem hiding this comment.
I'd put it right before the Configuration section. It's an extra feature that Connect supports that requires specific hardware, so I think it should be below sections that are applicable to a bigger user group.
Configuration is more like a reference section and anything below is not feature-related, hence this ordering where Hardware key support would be just above Configuration.
public-teleport-github-review-bot
bot
removed request for
r0mant,
mmcallister,
zmb3 and
xinding33
|
🤖 Vercel preview here: https://docs-6jx9gxblk-goteleport.vercel.app/docs/ver/preview |
The documentation isn't very extensive, but I wanted to avoid repeating information that we already have in https://goteleport.com/docs/admin-guides/access-controls/guides/hardware-key-support/
If you think we can add more here, I'm open to suggestions!