> 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/de/zertifikatsverwaltung/certificate-master/sub-ca-certificate.md).

# TLS-Inspektionszertifikat (Sub-CA)

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

{% hint style="info" %}
Diese Funktion erfordert Version **2.4** oder höher
{% endhint %}

In einigen Anwendungsfällen müssen Sie möglicherweise eine Sub CA der SCEPman RootCA ausstellen (z. B. damit eine Firewall TLS-Datenverkehr überprüfen kann). In diesem Fall können Sie manuell eine Sub CA erzeugen mit **Serverauthentifizierung** als EKU. Die PKCS#12-Datei ist mit dem auf dem Bildschirm angezeigten Passwort verschlüsselt. Sie können die PKCS#12-Datei mithilfe des Passworts direkt in das System importieren, in dem sie benötigt wird.

{% hint style="warning" %}
Beachten Sie, dass das Passwort nicht mehr zugänglich ist, sobald Sie diese Seite verlassen.
{% endhint %}

<figure><img src="https://2075553437-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LoGejQeUQcw7lqnQ3WX%2Fuploads%2FcQwgKmyjxqomYXHZfnii%2Fimage.png?alt=media&amp;token=24751248-98ea-42ab-a70e-4104de1c526a" 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/de/zertifikatsverwaltung/certificate-master/sub-ca-certificate.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.