> 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/fr/concepts/advanced-concepts/external-pam-integrations.md).

# Intégrations PAM externes

Les intégrations PAM externes connectent Devolutions Server et Remote Desktop Manager à des plateformes d'accès privilégié tierces pour la récupération des identifiants.

Les intégrations PAM externes permettent à Devolutions Server et à Remote Desktop Manager de fonctionner avec des plateformes tierces de gestion des accès privilégiés au lieu de stocker localement tous les identifiants privilégiés. Remote Desktop Manager demande les identifiants au PAM externe juste-à-temps et les injecte dans les sessions, tandis que Devolutions Server centralise le courtage des sessions, les approbations et l'audit permettant de savoir qui a utilisé quel compte. (docs.devolutions.net)

Cette approche permet aux organisations qui utilisent déjà des outils comme CyberArk ou d'autres solutions PAM de conserver leur cycle de vie des identifiants existant, tout en adoptant Devolutions Server et Devolutions PAM comme couche unifiée d'accès, de journalisation et d'application des politiques.

#### Sujets connexes

* [Intégrations PAM externes](https://docs.devolutions.net/rdm/fr/concepts/advanced-concepts/external-pam-integrations)
* [Devolutions PAM](https://docs.devolutions.net/pam/fr/)
* [Rapports PAM dans Devolutions Server](https://docs.devolutions.net/pam/fr/pam-with-devolutions-server/pam-reports-in-devolutions-server)


---

# 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/fr/concepts/advanced-concepts/external-pam-integrations.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.