> 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/purofairuno/jamf-pro.md).

# Jamf Pro

## 一般

{% hint style="success" %}
すべての 802.1X 関連ペイロードを **1 つの** Jamf の構成プロファイル - そして割り当てタイプ（コンピューター、デバイス、ユーザー）ごとに 1 つの構成プロファイル。&#x20;
{% endhint %}

802.1X を完全に構成するには、通常、次のペイロードが必要になります。

* ネットワーク ペイロード（WiFi および／または LAN）
* 証明書ペイロード
  * SCEP 発行 CA のルート CA 証明書
  * RADIUS サーバー証明書を発行する CA のルート CA 証明書（SCEP 発行 CA と同じでもかまいません）
* SCEP ペイロード（クライアント認証証明書）

<figure><img src="https://content.gitbook.com/content/SWU1DQ4UGkqER7uGNUOm/blobs/3ExgDEVV8kyAxBxpWcKV/image.png" alt=""><figcaption></figcaption></figure>

## ペイロード

{% content-ref url="/pages/17fdbde24989cf64da527e8fb01d3d6e0784ef8f" %}
[サーバー信頼](/ja/purofairuno/jamf-pro/server-trust.md)
{% endcontent-ref %}

{% content-ref url="/pages/dbfc23b8487e1fa5b1d86f87606432fcc1592884" %}
[WiFi プロファイル](/ja/purofairuno/jamf-pro/wifi-profile.md)
{% endcontent-ref %}

{% content-ref url="/pages/65e21b3864c6117f89241912c976bd665c2979b1" %}
[有線プロファイル](/ja/purofairuno/jamf-pro/wired-profile.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/purofairuno/jamf-pro.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.
