> 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/pt/configuracao/access-point-setup/radsec-available.md).
# RadSec
Mostrando o túnel exterior TLS e os certificados necessários
Antes de os seus pontos de acesso poderem estabelecer uma **ligação RadSec válida** (que pode ser considerada uma ligação mTLS), os seguintes requisitos devem ser cumpridos independentemente do fabricante do ponto de acesso.
* Os pontos de acesso requerem um **certificado de cliente válido** (normalmente designado como "Certificado de Cliente RadSec" ou "Certificado RadSec"). Este certificado de cliente deve ter a **EKU Autenticação de Cliente** (1.3.6.1.5.5.7.3.2) e **não Autenticação de Servidor**.
* Os pontos de acesso devem **confiar na AC** que emitiu o **Certificado do Servidor RADIUS**.
* O RADIUSaaS deve **confiar na AC** que emitiu o **certificado de cliente RadSec** nos seus pontos de acesso.
{% hint style="info" %}
O protocolo RadSec requer um segredo partilhado para calcular as verificações de integridade MD5.\
O [RFC do RadSec](https://datatracker.ietf.org/doc/html/rfc6614#:~:text=to%20implement\).%0A%0A%20%20%204.-,start,-exchanging%20RADIUS%20datagrams) define este segredo partilhado como a cadeia literal "radsec".
{% endhint %}
{% content-ref url="/pages/ee028991fca54a784f1a6f18ef7fbf61ed035bb3" %}
[Aruba](/pt/configuracao/access-point-setup/radsec-available/aruba.md)
{% endcontent-ref %}
{% content-ref url="/pages/64b35be2dfc18acdb2934992de12b0a0bf94c67e" %}
[FortiNet](/pt/configuracao/access-point-setup/radsec-available/fortinet.md)
{% endcontent-ref %}
{% content-ref url="/pages/65051107a80257acb3c09995fbc9a2691517d074" %}
[Juniper Mist](/pt/configuracao/access-point-setup/radsec-available/juniper-mist.md)
{% endcontent-ref %}
{% content-ref url="/pages/70e9ead4cd84fcde40806ccef194c09521eda6b9" %}
[Meraki](/pt/configuracao/access-point-setup/radsec-available/meraki.md)
{% endcontent-ref %}
{% content-ref url="/pages/ef4fbb53acff67d76c7b18f23b6387cbf0c2118d" %}
[MikroTik](/pt/configuracao/access-point-setup/radsec-available/mikrotik.md)
{% endcontent-ref %}
{% content-ref url="/pages/5866033d54975973d59178a4459cabdc3b562f28" %}
[Ruckus](/pt/configuracao/access-point-setup/radsec-available/ruckus.md)
{% endcontent-ref %}
{% content-ref url="/pages/4e428964c557042d5d9db583e13322f7a53466de" %}
[UniFi](/pt/configuracao/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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.radiusaas.com/pt/configuracao/access-point-setup/radsec-available.md?ask=&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.
