> 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/authentication.md).

# Autenticación

La autenticación en Devolutions Server verifica la identidad del usuario mediante cuentas locales o proveedores externos como Active Directory y Azure AD.

La autenticación en Devolutions Server es el proceso de verificar la identidad de un usuario antes de concederle acceso a las bóvedas y a las funciones administrativas. Puede basarse en cuentas locales o en proveedores de identidad externos como Active Directory, Azure AD u otras plataformas SSO, y normalmente se combina con la autenticación multifactor para obtener una mayor garantía.

Una vez autenticados, los usuarios reciben permisos a través de roles y grupos, y las credenciales se gestionan en su nombre al iniciar conexiones. Esta separación entre identidad, autorización y uso de credenciales ayuda a reducir el movimiento lateral y respalda los requisitos de cumplimiento normativo para la gestión de accesos privilegiados.

#### Temas relacionados

* [Gestión de usuarios y seguridad](/server/es/web-interface/administration/user-and-security-management.md)


---

# 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/authentication.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.