> 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/es/configuracion/access-point-setup/radsec-available.md).

# RadSec

<figure><img src="/files/fa2520da08541e1d507ff78a1c4812f0b4852e64" alt=""><figcaption><p>Mostrando el túnel externo TLS y los certificados requeridos</p></figcaption></figure>

Antes de que sus puntos de acceso puedan establecer una **conexión RadSec** (que puede considerarse una conexión mTLS), deben cumplirse los siguientes requisitos independientemente del fabricante del punto de acceso.

* Los puntos de acceso requieren un **certificado de cliente** (normalmente denominado "Certificado de cliente RadSec" o "Certificado RadSec"). Este certificado de cliente debe tener la **EKU de autenticación de cliente** (1.3.6.1.5.5.7.3.2) y **no autenticación de servidor**.
* Los puntos de acceso deben **confiar en la CA** que emitió el **certificado del servidor RADIUS**.
* RADIUSaaS debe **confiar en la CA** que emitió el **certificado de cliente RadSec** en sus puntos de acceso.

{% hint style="info" %}
El protocolo RadSec requiere un secreto compartido para calcular las comprobaciones de integridad MD5.\
El [RFC de RadSec](https://datatracker.ietf.org/doc/html/rfc6614#:~:text=to%20implement\).%0A%0A%20%20%204.-,start,-exchanging%20RADIUS%20datagrams) define este secreto compartido como la cadena literal "radsec".
{% endhint %}

{% content-ref url="/pages/c5def68e6d1042098a6eeb76396402f84a1f4931" %}
[Aruba](/es/configuracion/access-point-setup/radsec-available/aruba.md)
{% endcontent-ref %}

{% content-ref url="/pages/a73ab9fc886b4a39909b1c60c991491c71e730de" %}
[FortiNet](/es/configuracion/access-point-setup/radsec-available/fortinet.md)
{% endcontent-ref %}

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

{% content-ref url="/pages/dfbf64c5f86d5f5ee86ba78c27c2ccdc846c0baa" %}
[Meraki](/es/configuracion/access-point-setup/radsec-available/meraki.md)
{% endcontent-ref %}

{% content-ref url="/pages/2edee7d7bfeae496a980fa43a64caf2d9b9d2e2a" %}
[MikroTik](/es/configuracion/access-point-setup/radsec-available/mikrotik.md)
{% endcontent-ref %}

{% content-ref url="/pages/11398d9bdc4f0f31e198f756e540dbb25bad1f51" %}
[Ruckus](/es/configuracion/access-point-setup/radsec-available/ruckus.md)
{% endcontent-ref %}

{% content-ref url="/pages/7e5d814ac5e21a6a0acbc54c8630c5b39115ecdf" %}
[UniFi](/es/configuracion/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/es/configuracion/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.