> 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/de/konfiguration/access-point-setup/radsec-available.md).
# RadSec
Anzeige des äußeren TLS-Tunnels und der erforderlichen Zertifikate
Bevor Ihre Access Points in der Lage sind, eine gültige **RadSec-Verbindung** (die als eine mTLS-Verbindung betrachtet werden kann), müssen unabhängig vom Hersteller des Access Points die folgenden Anforderungen erfüllt sein.
* Access Points benötigen ein gültiges **Client-Zertifikat** (üblicherweise als „RadSec-Client-Zertifikat“ oder „RadSec-Zertifikat“ bezeichnet). Dieses Client-Zertifikat muss die **EKU Client-Authentifizierung** (1.3.6.1.5.5.7.3.2) und **nicht Server Authentication**.
* Access Points müssen **der CA vertrauen** die das **RADIUS-Server-Zertifikat**.
* RADIUSaaS muss **der CA vertrauen** die das **RadSec-Client-Zertifikat** auf Ihren Access Points.
{% hint style="info" %}
Das RadSec-Protokoll erfordert ein gemeinsames Geheimnis, um die MD5-Integritätsprüfungen zu berechnen.\
Das [RadSec-RFC](https://datatracker.ietf.org/doc/html/rfc6614#:~:text=to%20implement\).%0A%0A%20%20%204.-,start,-exchanging%20RADIUS%20datagrams) definiert dieses gemeinsame Geheimnis als den Literalstring "radsec".
{% endhint %}
{% content-ref url="/pages/116695f613b3488f8c53bca5564ed3fb722301a5" %}
[Aruba](/de/konfiguration/access-point-setup/radsec-available/aruba.md)
{% endcontent-ref %}
{% content-ref url="/pages/cd2486842d2e725f338aeb3713a410c9ac33ca91" %}
[FortiNet](/de/konfiguration/access-point-setup/radsec-available/fortinet.md)
{% endcontent-ref %}
{% content-ref url="/pages/498c6c40222ef8b7e1fb51d9c82065d8942835ee" %}
[Juniper Mist](/de/konfiguration/access-point-setup/radsec-available/juniper-mist.md)
{% endcontent-ref %}
{% content-ref url="/pages/a617e1982e729c2a090c3facf2be172bb4010e45" %}
[Meraki](/de/konfiguration/access-point-setup/radsec-available/meraki.md)
{% endcontent-ref %}
{% content-ref url="/pages/4df72e7b1746c3b695c45a65a9a5554e77328d36" %}
[MikroTik](/de/konfiguration/access-point-setup/radsec-available/mikrotik.md)
{% endcontent-ref %}
{% content-ref url="/pages/51407ec2ccff3e73965b03b729044fbe32f96c73" %}
[Ruckus](/de/konfiguration/access-point-setup/radsec-available/ruckus.md)
{% endcontent-ref %}
{% content-ref url="/pages/cabf0078734757c93de73bed827ac33dcb13a036" %}
[UniFi](/de/konfiguration/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/de/konfiguration/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.
