> For the complete documentation index, see [llms.txt](https://docs.radiusaas.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.radiusaas.com/fr/configuration/access-point-setup/radsec-available.md).

# RadSec

<figure><img src="/files/3eff2383529e56c8a5c9e1ad67f8628e7338759e" alt=""><figcaption><p>Affichage du tunnel externe TLS et des certificats requis</p></figcaption></figure>

Avant que vos points d'accès puissent établir une connexion valide **connexion RadSec** (qui peut être considérée comme une connexion mTLS), les exigences suivantes doivent être respectées, quel que soit le fabricant du point d'accès.

* Les points d'accès nécessitent un **certificat client** (généralement appelé « certificat client RadSec » ou « certificat RadSec »). Ce certificat client doit avoir le **EKU Authentification du client** (1.3.6.1.5.5.7.3.2) et **non l’authentification du serveur**.
* Les points d'accès doivent **faire confiance à l'AC** qui a émis le **certificat du serveur RADIUS**.
* RADIUSaaS doit **faire confiance à l'AC** qui a émis le **certificat client RadSec** sur vos points d'accès.

{% hint style="info" %}
Le protocole RadSec nécessite un secret partagé pour calculer les vérifications d'intégrité MD5.\
Le [RFC RadSec](https://datatracker.ietf.org/doc/html/rfc6614#:~:text=to%20implement\).%0A%0A%20%20%204.-,start,-exchanging%20RADIUS%20datagrams) définit ce secret partagé comme la chaîne littérale « radsec ».
{% endhint %}

{% content-ref url="/pages/67407186b55884ddc71444665d0b0b4de217598d" %}
[Aruba](/fr/configuration/access-point-setup/radsec-available/aruba.md)
{% endcontent-ref %}

{% content-ref url="/pages/4400ec4b22de95641bc22a19af3d9222ae73173f" %}
[FortiNet](/fr/configuration/access-point-setup/radsec-available/fortinet.md)
{% endcontent-ref %}

{% content-ref url="/pages/ed0c7f4128725dbea4829486d0ba6f5690021c98" %}
[Juniper Mist](/fr/configuration/access-point-setup/radsec-available/juniper-mist.md)
{% endcontent-ref %}

{% content-ref url="/pages/9b284d4e90a5c14137abbc6434f94da9c2c0f520" %}
[Meraki](/fr/configuration/access-point-setup/radsec-available/meraki.md)
{% endcontent-ref %}

{% content-ref url="/pages/c2fa59a9d78e9fb65f3e3e3b4407dfc91dce46c9" %}
[MikroTik](/fr/configuration/access-point-setup/radsec-available/mikrotik.md)
{% endcontent-ref %}

{% content-ref url="/pages/10e43154b212ad3f4d3e950c25c96d097c413506" %}
[Ruckus](/fr/configuration/access-point-setup/radsec-available/ruckus.md)
{% endcontent-ref %}

{% content-ref url="/pages/dad317c5f85fa731ea0caa7afebf6dc26a07a855" %}
[UniFi](/fr/configuration/access-point-setup/radsec-available/unifi.md)
{% endcontent-ref %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.radiusaas.com/fr/configuration/access-point-setup/radsec-available.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.