Skip to content

[Bug]: Passthrough header parameters not persisted to database #861

@ankit-gajera-merck

Description

@ankit-gajera-merck

🐞 Bug Summary

Despite setting ENABLE_HEADER_PASSTHROUGH=true in the environment (e.g., .env), passthrough header parameters are not being saved in the database.

🧩 Affected Component

Select the area of the project impacted:

  • mcpgateway - API
  • mcpgateway - UI (admin panel)
  • mcpgateway.wrapper - stdio wrapper
  • Federation or Transports
  • CLI, Makefiles, or shell scripts
  • Container setup (Docker/Podman/Compose)
  • Other (explain below)

🔁 Steps to Reproduce

  1. Clone the repo and checkout tag v0.6.0.
  2. In your .env configuration, set:
    ENABLE_HEADER_PASSTHROUGH=true
  3. Launch the server and open the Admin UI.
  4. Create a gateway with Passthrough Headers: email, authorization.
  5. After the gateway is successfully added, click Edit—the Passthrough Headers field is empty.
  6. In the database, within the gateways table, check the passthrough_headers column for this gateway—it is NULL.

🤔 Expected Behavior

After the gateway is successfully added, click Edit—the Passthrough Headers field should be filled with added header keys.
By adding them in the database directly as ["email", "authorization"], it is showing as expected.


📓 Logs / Error Output

Couldn't see any error logs in the console.


🧠 Environment Info

You can retrieve most of this from the /version endpoint.

Key Value
Version or commit 0.6.0
Runtime Python 3.12, Gunicorn
Platform / OS AWS Amazon Linux 2
Container none

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingtriageIssues / Features awaiting triage

Type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions