shankar0123 743dca2fb3 fix: use real X.509 certs in EST handler tests ...

EST handler tests used fake PEM data (e.g., "MIIBmjCCAUCgAwIBAgIRATest")
which is invalid base64 (25 chars, not divisible by 4). Go's pem.Decode
fails silently, causing pemToDERChain to return "no certificates found"
and tests to get 500 instead of 200.

Added generateTestCertPEM() helper that creates a real self-signed ECDSA
P-256 certificate, used across all EST handler tests that need cert PEM.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

2026-03-25 15:55:26 -04:00

..

api

fix: use real X.509 certs in EST handler tests

2026-03-25 15:55:26 -04:00

cli

feat: M17 OpenSSL/Custom CA issuer connector + M16b CLI tool with bulk import

2026-03-23 18:12:40 -04:00

config

feat: add EST server (RFC 7030) for device certificate enrollment (M23)

2026-03-25 15:31:06 -04:00

connector

feat: add EST server (RFC 7030) for device certificate enrollment (M23)

2026-03-25 15:31:06 -04:00

domain

feat: add EST server (RFC 7030) for device certificate enrollment (M23)

2026-03-25 15:31:06 -04:00

integration

feat: add EST server (RFC 7030) for device certificate enrollment (M23)

2026-03-25 15:31:06 -04:00

mcp

fix: Go 1.25 upgrade, codebase audit fixes, MCP server tests

2026-03-23 17:36:25 -04:00

repository

feat: add network certificate discovery (M21) and Prometheus metrics (M22)

2026-03-24 23:37:47 -04:00

scheduler

feat: add network certificate discovery (M21) and Prometheus metrics (M22)

2026-03-24 23:37:47 -04:00

service

fix: add GetCACertPEM to connector-layer mock for go vet

2026-03-25 15:48:49 -04:00