[Bug]: Authentication is Broken - Unauthorized Error in mailcomposer example

[amorandi-cisco]

Bug Description

Authentication appears to be broken in mailcomposer example. Both Swagger UI and console-based API requests are consistently returning "Error: Unauthorized."
{
"detail": "Invalid API Key"
}

Expected Behavior

Authentication should succeed with valid credentials, granting access to protected API endpoints and returning an HTTP 200 (OK) status code.

Affected Version

v1.0.0

Steps to Reproduce

deploy mailcomposer example, e.g.
wfsm deploy -m ./mailcomposer.json -e mailcomposer_example.yaml

1. Try to log in via Swagger.
2. or via curl (or similar).

Expected: HTTP 200 (OK) status code.

Actual: "Error: 401 Unauthorized."
{
"detail": "Invalid API Key"
}

Checklist

• I have read the contributing guidelines
• I have verified this does not duplicate an existing issue