> 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).

# 証明書マスター

Certificate Master UI を通じて証明書を発行、管理、失効できます。

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

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

Certificate Master は、証明書の発行、確認、管理を行うための SCEPman の Web UI です。独立した App Service として稼働し、通常は次の `-cm` というサフィックスで識別されます。

{% hint style="info" %}
開始する前に、アカウントに Certificate Master のロールを割り当ててください。
{% endhint %}

### はじめに

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

### 発行済み証明書の管理

SCEPman PKI によって発行された証明書を検索、確認、失効します。

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

### 証明書のワークフローを選択

<table data-view="cards"><thead><tr><th>ワークフロー</th><th data-card-target data-type="content-ref">ガイド</th></tr></thead><tbody><tr><td><i class="fa-file-signature">:file-signature:</i> 既存の証明書要求に署名する</td><td><a href="https://docs.scepman.com/ja/zheng-ming-shu-guan-li/certificate-master/certificate-signing-request-csr.md">証明書署名要求 (CSR)</a></td></tr><tr><td><i class="fa-server">:server:</i> TLS サーバー証明書</td><td><a href="https://docs.scepman.com/ja/zheng-ming-shu-guan-li/certificate-master/tls-server-certificate-pkcs-12.md">TLS サーバー証明書</a></td></tr><tr><td><i class="fa-shield-halved">:shield-halved:</i> TLS インスペクション用下位 CA 証明書</td><td><a href="https://docs.scepman.com/ja/zheng-ming-shu-guan-li/certificate-master/sub-ca-certificate.md">TLS インスペクション (Sub CA) 証明書</a></td></tr><tr><td><i class="fa-code">:code:</i> コード署名証明書</td><td><a href="https://docs.scepman.com/ja/zheng-ming-shu-guan-li/certificate-master/code-signing-certificate.md">コード署名証明書</a></td></tr><tr><td><i class="fa-laptop">:laptop:</i> デバイス証明書</td><td><a href="https://docs.scepman.com/ja/zheng-ming-shu-guan-li/certificate-master/client-certificate-pkcs-12.md">デバイス証明書</a></td></tr><tr><td><i class="fa-user">:user:</i> ユーザー証明書</td><td><a href="https://docs.scepman.com/ja/zheng-ming-shu-guan-li/certificate-master/user-certificate.md">ユーザー証明書</a></td></tr></tbody></table>

### 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.
