mirror of
https://github.com/hanzoai/kms.git
synced 2026-10-17 11:18:16 +00:00
zeekay
0ebffbd529
- Fix 381 files where branding script corrupted variable names (e.g. isHanzo KMSTemplate -> isKmsTemplate) - Rebrand from "Hanzo KMS" to just "KMS" for white-label support (allows Lux KMS, Hanzo KMS, etc. via configuration) - 856 files, purely string replacements, no logic changes
27 lines
1.1 KiB
Plaintext
27 lines
1.1 KiB
Plaintext
---
|
|
title: "Adding Custom Certificates"
|
|
description: "Learn how to configure KMS with custom certificates"
|
|
---
|
|
|
|
By default, the KMS Docker image includes certificates from well-known public certificate authorities.
|
|
However, some integrations with KMS may need to communicate with your internal services that use private certificate authorities.
|
|
To configure trust for custom certificates, follow these steps. This is particularly useful for connecting KMS with self-hosted services like GitLab.
|
|
|
|
## Prerequisites
|
|
|
|
- Docker
|
|
- Standalone [KMS image](https://hub.docker.com/r/ghcr.io/hanzoai/kms)
|
|
- Certificate public key `.crt` files
|
|
|
|
## Setup
|
|
|
|
1. Place all your public key `.crt` files into a single directory.
|
|
2. Mount the directory containing the `.crt` files to the `/usr/local/share/ca-certificates/` path in the KMS container.
|
|
3. Set the following environment variable on your KMS container:
|
|
```
|
|
NODE_EXTRA_CA_CERTS=/etc/ssl/certs/ca-certificates.crt
|
|
```
|
|
4. Start the KMS container.
|
|
|
|
By following these steps, your KMS container will trust the specified certificates, allowing you to securely connect KMS to your internal services.
|