> For the complete documentation index, see [llms.txt](https://help.glpi-project.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.glpi-project.org/documentation/fr/modules/setup/authentication/imap.md).

# Authentification depuis IMAP

L'interfaçage de GLPI avec les serveurs de messagerie comme source d'authentification.

Cette source d'authentification se configure depuis le menu `Configuration > Authentification > Serveurs de messagerie`.

Cette capacité peut compenser l'absence de répertoire ou de serveur CAS. Cependant, contrairement à ce qui est possible avec d'autres sources d'authentification, aucun import de masse n'est disponible. Un utilisateur est authentifié par GLPI si le serveur de messagerie l'a authentifié au préalable.

La connexion au serveur de messagerie utilise les protocoles IMAP ou POP. Les options de chiffrement SSL et TLS sont disponibles. La distinction est faite entre le domaine de messagerie qui est la partie de l'adresse mail qui suit le caractère astérisque, et le nom de domaine complet du serveur de messagerie, qui peut servir plusieurs domaines de messagerie.


---

# 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://help.glpi-project.org/documentation/fr/modules/setup/authentication/imap.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.