> For the complete documentation index, see [llms.txt](https://docs.scepman.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scepman.com/ja/zheng-ming-shu-guan-li/certificate-master.md).

# 証明書マスター

{% hint style="warning" %}
SCEPman Enterprise Edition のみ
{% endhint %}

## 概要

{% embed url="<https://youtu.be/kr8uBPlG4J8?t=122>" %}
SCEPman Certificate Master クイック概要
{% endembed %}

Certificate Master は、各 SCEPman デプロイメント内の 2 つ目の App Service で、App Service 名の「-cm」表記（変更されていない場合）で識別できます。

以下のサイトでは、一般的なユースケースで Certificate Master UI を通じて証明書を発行する方法について、詳細な情報を提供しています。

{% content-ref url="/pages/64fe198a8bf5d86e7c799e649274e13e6b73751d" %}
[証明書を管理する](/ja/zheng-ming-shu-guan-li/certificate-master/manage-certificates.md)
{% endcontent-ref %}

{% content-ref url="/pages/29f64cc9492a6b8f290bf5df488ee01052c48b59" %}
[証明書署名要求 (CSR)](/ja/zheng-ming-shu-guan-li/certificate-master/certificate-signing-request-csr.md)
{% endcontent-ref %}

{% content-ref url="/pages/0ef253615e16cbb77f9a257844a3af96f02fc64a" %}
[TLS サーバー証明書](/ja/zheng-ming-shu-guan-li/certificate-master/tls-server-certificate-pkcs-12.md)
{% endcontent-ref %}

{% content-ref url="/pages/d5b79a8609c9fb429e8fa09be9793744f5f72057" %}
[TLS インスペクション (Sub CA) 証明書](/ja/zheng-ming-shu-guan-li/certificate-master/sub-ca-certificate.md)
{% endcontent-ref %}

{% content-ref url="/pages/fb3e5d5d4b0bc2bf668ddd7aefbb45ebf03dad21" %}
[コード署名証明書](/ja/zheng-ming-shu-guan-li/certificate-master/code-signing-certificate.md)
{% endcontent-ref %}

{% content-ref url="/pages/5fe61b25c976ce21a3036aeef0b5044674f57c30" %}
[デバイス証明書](/ja/zheng-ming-shu-guan-li/certificate-master/client-certificate-pkcs-12.md)
{% endcontent-ref %}

{% content-ref url="/pages/08b55507796c57fd224cb82fa16ccd2200bee2ad" %}
[ユーザー証明書](/ja/zheng-ming-shu-guan-li/certificate-master/user-certificate.md)
{% endcontent-ref %}

## はじめに

Certificate Master にアクセスするには、まず対象のロールをユーザーアカウントに割り当てる必要があります。Certificate Master's Role-Based Access Control に関する次の記事をご参照ください。

{% content-ref url="/pages/89fcf39f72fa6a350a1fcf569e8e1487783f9f0e" %}
[証明書マスター RBAC](/ja/scepman-gou-cheng/rbac.md)
{% endcontent-ref %}

## Certificate Master のホームページ:

<figure><img src="https://114237723-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LoGejQeUQcw7lqnQ3WX%2Fuploads%2FA4fJCZ8AKKw1AtWToXnn%2Fimage.png?alt=media&amp;token=b20c5b1b-059e-4192-953e-ab39a7967f52" alt=""><figcaption></figcaption></figure>


---

# 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.scepman.com/ja/zheng-ming-shu-guan-li/certificate-master.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.