# Secret Type - CERTJKS

The CERTJKS-Type is the same as the [CERT-Type](/supported-secret-types/secret-type-cert.md). The only difference is that it converts the saved Certificate into a Java Key Store.

### How To

First please read the part of [CERT-TYPE](/supported-secret-types/secret-type-cert.md), because the Vault-CRD expects the Certificate in a specific format.

After this you can create the following Vault resource in Kubernetes:

```yaml
apiVersion: "koudingspawn.de/v1"
kind: Vault
metadata:
  name: test-certjks
spec:
  path: "secret/test-url.example.com"
  type: "CERTJKS"
```

This will generate the Vault resource and also the secret:

```
$ kubectl get vault test-certjks
NAME           AGE
test-certjks   8d
```

```
$ kubectl get secret test-certjks
NAME           TYPE      DATA      AGE
test-certjks   Opaque    1         8d
```

By default the Key Store is saved in the key.jks path. You can change it with the [jksConfiguration](/supported-secret-types/secret-type-pkijks.md#jksconfiguration) as described in [PKIJKS](/supported-secret-types/secret-type-pkijks.md#jksconfiguration).

### Change Adjustment Callback

For more details please see [Change Detection](/change-detection.md)!


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://vault.koudingspawn.de/supported-secret-types/secret-type-certjks.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.