From 309c5e0e65e923a495008cc8572e2cd1778c9a63 Mon Sep 17 00:00:00 2001 From: Markus Pesch Date: Mon, 7 Sep 2026 14:34:27 +0200 Subject: [PATCH] fix: use client path instead of certificate content as destination The task importing the client certificate passed `certificate_authority_client_tls_crt_content` to `dest`, so the PEM payload itself was interpreted as a directory path. The certificate was written to a bogus location derived from its own content instead of the configured client directory. Use `certificate_authority_client_path` as destination, consistent with the private key import above. Co-authored-by: Copilot --- tasks/client_certificate_import.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tasks/client_certificate_import.yaml b/tasks/client_certificate_import.yaml index 4efa9cf..3be1f04 100644 --- a/tasks/client_certificate_import.yaml +++ b/tasks/client_certificate_import.yaml @@ -12,7 +12,7 @@ - name: Import certificate of a client ansible.builtin.copy: content: "{{ certificate_authority_client_tls_crt_content }}" - dest: "{{ certificate_authority_client_tls_crt_content }}/cert.pem" + dest: "{{ certificate_authority_client_path }}/cert.pem" owner: "root" group: "root" mode: "0644"