mirror of
https://github.com/taylanbakircioglu/haproxy-openmanager.git
synced 2026-09-18 08:35:28 +00:00
taylanbakircioglu
09157e8be1
CRITICAL HAProxy Validation Fix: Bulk import was creating configs that fail HAProxy validation HAProxy Validation Error: server es1 ... ssl verify required ALERT: verify is enabled but no CA file specified Root Cause: Original config: ssl verify required ca-file /path/cert.pem After parse: ssl verify required (ca-file removed) Result: HAProxy validation FAILS HAProxy Requirement: verify required → MUST have ca-file verify none → Can work without ca-file ssl (no verify) → Uses default verification Fix Applied (Line 677-704): When parsing server with both verify AND ca-file: 1. Detect: verify=required + ca-file exists 2. Remove ca-file (as planned) 3. Change verify to 'none' (NEW - prevents validation error) 4. Warning: Explain user needs to reconfigure after import Three Scenarios Handled: 1. verify + ca-file → verify=none, remove ca-file, warn user 2. verify only → keep verify as-is 3. ca-file only → set verify=none, remove ca-file, warn user Generated Config Now: Before: server es1 ... ssl verify required (FAILS validation) After: server es1 ... ssl verify none (PASSES validation) User Workflow: 1. Bulk import → Servers created with verify=none 2. HAProxy validation → PASSES 3. User edits server → Selects SSL cert → Sets verify=required 4. Apply → Config generated with ca-file path 5. HAProxy validation → PASSES (has ca-file) Warning Message: 'verify required' changed to 'none' to pass HAProxy validation After import, select SSL certificate and set verify to 'required' Impact: Bulk import now creates HAProxy-valid configurations