> 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/ja/she-ding/access-point-setup/radsec-available.md).

# RadSec

<figure><img src="https://992520889-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSWU1DQ4UGkqER7uGNUOm%2Fuploads%2FSPYhaqJKWvpS6cxKGAbt%2Fimage.png?alt=media&amp;token=68f6fd36-1ac8-46d4-bb0a-afcdfdb87892" alt=""><figcaption><p>TLS外側トンネルと必要な証明書を表示</p></figcaption></figure>

アクセスポイントが有効な **RadSec接続** （これはmTLS接続とみなすことができます）、アクセスポイントのメーカーに関係なく、以下の要件を満たす必要があります。

* アクセスポイントには有効な **クライアント証明書** （通常は「RadSecクライアント証明書」または「RadSec証明書」と呼ばれます）。このクライアント証明書には次のものが必要です **EKU クライアント認証** （1.3.6.1.5.5.7.3.2）および **サーバー認証ではない**.
* アクセスポイントは **CAを信頼する** を発行した **RADIUSサーバー証明書**.
* RADIUSaaSは **CAを信頼する** を発行した **RadSecクライアント証明書** をあなたのアクセスポイント上で。

{% hint style="info" %}
RadSecプロトコルは、MD5整合性チェックを計算するために共有シークレットを必要とします。\
その [RadSec RFC](https://datatracker.ietf.org/doc/html/rfc6614#:~:text=to%20implement\).%0A%0A%20%20%204.-,start,-exchanging%20RADIUS%20datagrams) この共有シークレットを文字列リテラル「radsec」と定義しています。
{% endhint %}

{% content-ref url="/pages/856e8728d5ff84e2d50b58aea1c8f1d353d737ef" %}
[Aruba](/ja/she-ding/access-point-setup/radsec-available/aruba.md)
{% endcontent-ref %}

{% content-ref url="/pages/1b7d499319cbc2f9037e887d628f7bc5d0f6b60a" %}
[FortiNet](/ja/she-ding/access-point-setup/radsec-available/fortinet.md)
{% endcontent-ref %}

{% content-ref url="/pages/2837c6991116b3c816dd343fdccc1b5a93699091" %}
[Juniper Mist](/ja/she-ding/access-point-setup/radsec-available/juniper-mist.md)
{% endcontent-ref %}

{% content-ref url="/pages/8f03d32ad030e77e874f516f769f6ce045192d77" %}
[Meraki](/ja/she-ding/access-point-setup/radsec-available/meraki.md)
{% endcontent-ref %}

{% content-ref url="/pages/4f24815d306fa494683d431e16b2584269939ea4" %}
[MikroTik](/ja/she-ding/access-point-setup/radsec-available/mikrotik.md)
{% endcontent-ref %}

{% content-ref url="/pages/e55bc3b1fba4988d81e4b24cbeff020234c8c269" %}
[Ruckus](/ja/she-ding/access-point-setup/radsec-available/ruckus.md)
{% endcontent-ref %}

{% content-ref url="/pages/e3cc9eeb56a72a10f25f8ef0f3be83acb3b8f201" %}
[UniFi](/ja/she-ding/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/ja/she-ding/access-point-setup/radsec-available.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.