> For the complete documentation index, see [llms.txt](https://hacking-notes.jord4n.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hacking-notes.jord4n.pro/fr/active-directory/credentials/non-interactive-authentication.md).

# Authentification non interactive

Notes de sécurité Active Directory pour l'authentification non interactive, couvrant l'énumération, Kerberos, les identifiants, l'abus des ACL, le mouvement latéral, le flux de travail d'exploitation et les étapes de validation.

#### Définition

L'authentification non interactive est utilisée après une authentification interactive réussie.

Dans ce cas, l'utilisateur ne ressaisit pas ses identifiants.

Windows réutilise les informations déjà établies pour accéder aux services réseau.

Exemples :

* accès à un partage SMB ;
* connexion à une autre machine ;
* accès à un service distant ;
* Utilisation de Kerberos pour demander un ticket de service.

<figure><img src="https://3840167291-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-1522476455912628c8167bb27486caabd4a2275d%2Fimage%20(3288).png?alt=media" alt="" width="370"><figcaption></figcaption></figure>

#### Exemple dans le labo

Depuis une session authentifiée, vous pouvez accéder à un partage administratif :

```bash
cd //WS01/c$
```

Si l'utilisateur dispose des droits nécessaires, Windows ne redemande pas nécessairement les identifiants.

Le système réutilise la session existante et le mécanisme d'authentification réseau, souvent via Kerberos.

{% embed url="<https://learn.microsoft.com/en-us/sysinternals/downloads/logonsessions>" %}


---

# 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://hacking-notes.jord4n.pro/fr/active-directory/credentials/non-interactive-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.