Skip to content

[Auto-Translate] [Test] Screenshot scope=pr (1780360407) #397

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
hyunil-shin wants to merge 2 commits into from
Closed

[Auto-Translate] [Test] Screenshot scope=pr (1780360407) #397

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
bbba06f
Translate ko/privateca-scope.md -> en/privateca-scope.md
hyunil-shin Jun 2, 2026
2ea7fc2
Translate ko/privateca-scope.md -> ja/privateca-scope.md
hyunil-shin Jun 2, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 28 additions & 0 deletions en/privateca-scope.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,28 @@
# Console Guide
**Management > Private CA > Console Guide**

The Private CA console is organized around certificate authorities (CAs), and all resources (certificate templates, issuers, certificates, ACME tokens) belong to a specific store. The console screen has a tab structure with a list of stores on the left and detailed information of the selected store on the right.

## Private CA Usage Flow

The process for issuing certificates in Private CA is as follows:

1. **Create Store**: Create a space to manage certificates.
2. **Create Issuer**: Create a certificate authority (CA) to sign certificates.
- Root CA: Top-level certificate authority
- Intermediate CA: Intermediate certificate authority under the Root CA
3. **Create Certificate Template**: Used when issuing multiple certificates with the same settings.
4. **Issue Certificate**: Issue certificates for actual use through certificate templates.

!!! tip "Note"
- **CA (certificate authority)**: The entity that issues and signs certificates.
- **Root CA**: A self-signed top-level certificate. It is the starting point of all trust.
- **Intermediate CA**: An intermediate certificate signed by the Root CA. Used for issuing actual server certificates.

![Private CA Console Screen](https://static.toastoven.net/prod2_translate-test/en/privateca.png)

## Additional Images

![Pre-existing Image (Not included in PR)](../images/preexisting.png)

![External Screenshot (Not included in PR)](http://static.toastoven.net/prod_ai_easymaker/console-guide_appendix_hyperparameter_ko.png)
28 changes: 28 additions & 0 deletions ja/privateca-scope.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,28 @@
# コンソール使用ガイド
**Management > Private CA > コンソール使用ガイド**

Private CAコンソールは、認証機関(certificate authority, CA)を中心に構成されており、すべてのリソース(証明書テンプレート、発行者、証明書、ACMEトークン)は特定のストレージに属します。コンソール画面は、左側にストレージリスト、右側に選択したストレージの詳細情報を表示するタブ構造になっています。

## Private CA使用フロー

Private CAで証明書を発行するまでの過程は次の通りです。

1. **ストレージ作成**: 証明書を管理するスペースを作ります。
2. **発行者作成**: 証明書に署名する認証機関(CA)を作ります。
- Root CA: 最上位認証機関
- Intermediate CA: Root CA下の中間認証機関
3. **証明書テンプレート作成**: 同じ設定で複数の証明書を発行する時に使用します。
4. **証明書発行**: 証明書テンプレートを通じて実際に使用する証明書を発行します。

!!! tip "知っておくべきこと"
- **CA(certificate authority, 認証機関)**: 証明書を発行し署名する主体です。
- **Root CA**: 自己署名した最上位証明書です。すべての信頼の出発点です。
- **Intermediate CA**: Root CAによって署名された中間証明書です。実際のサーバー証明書発行に使用されます。

![Private CAコンソール画面](https://static.toastoven.net/prod2_translate-test/ja/privateca.png)

## 追加画像

![事前存在画像(PR未含)](../images/preexisting.png)

![外部スクリーンショット(PR未含)](http://static.toastoven.net/prod_ai_easymaker/console-guide_appendix_hyperparameter_ko.png)