> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/server/es/concepts/intermediate-concepts/ssh-key.md).

# Clave SSH

Una clave SSH en Devolutions Server es una entrada de credencial almacenada que contiene un par de claves utilizado para autenticar sesiones SSH sin una contraseña reutilizable.

Una clave SSH es un par de claves criptográficas que se utiliza para autenticarse en servidores SSH sin enviar una contraseña reutilizable. La clave privada permanece almacenada de forma segura, mientras que la clave pública se instala en los sistemas de destino para que los clientes puedan demostrar su identidad durante la conexión.

En Devolutions Server, las claves SSH se almacenan como entradas de credenciales en bóvedas y son utilizadas por herramientas como Remote Desktop Manager, Devolutions Launcher o el cliente web al abrir sesiones SSH. Centralizar las claves simplifica la rotación, ayuda a aplicar políticas de longitud y algoritmo de clave, y garantiza que los registros de auditoría muestren exactamente qué clave y qué usuario accedieron a un sistema.

#### Véase también

* [Niveles de integración](https://docs.devolutions.net/resources/es/integration-levels#credential-management)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.devolutions.net/server/es/concepts/intermediate-concepts/ssh-key.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.