8ee362744b
@jefferai and I discussed this on Friday. With three fully-documented SSH backends, the page is lengthy, ungreppable, and intimidating. This commit separates the SSH backends into their own pages with as little text changes as possible.
35 lines
1.2 KiB
Markdown
35 lines
1.2 KiB
Markdown
---
|
|
layout: "docs"
|
|
page_title: "SSH Secret Backend"
|
|
sidebar_current: "docs-secrets-ssh"
|
|
description: |-
|
|
The Vault SSH secret backend provides secure authentication and authorization
|
|
for access to machines via the SSH protocol. There are multiple modes to the
|
|
Vault SSH backend including signed SSH certificates, dynamic SSH keys, and
|
|
one-time passwords.
|
|
---
|
|
|
|
# SSH Secret Backend
|
|
|
|
Name: `ssh`
|
|
|
|
The Vault SSH secret backend provides secure authentication and authorization
|
|
for access to machines via the SSH protocol. The Vault SSH backend helps manage
|
|
access to machine infrastructure, providing several ways to issue SSH
|
|
credentials.
|
|
|
|
The Vault SSH secret backend supports the following modes. Each mode is
|
|
individually documented on its own page.
|
|
|
|
- [Signed SSH Certificates](/docs/secrets/ssh/signed-ssh-certificates.html)
|
|
- [One-time SSH Passwords](/docs/secrets/ssh/one-time-ssh-passwords.html)
|
|
- [Dynamic SSH Keys](/docs/secrets/ssh/dynamic-ssh-keys.html) <sup>DEPRECATED</sup>
|
|
|
|
All guides assume a basic familiarity with the SSH protocol.
|
|
|
|
## API
|
|
|
|
The SSH secret backend has a full HTTP API. Please see the
|
|
[SSH secret backend API](/api/secret/ssh/index.html) for more
|
|
details.
|