Add ApiKeyMediator block to api_product_template.xml#14094
Add ApiKeyMediator block to api_product_template.xml#14094Tharsanan1 wants to merge 1 commit intowso2:masterfrom
Conversation
API Products were missing the ApiKeyMediator configuration in their Velocity template, causing API key endpoint security headers (e.g., x-api-key for AI APIs) to never be forwarded to backend services. This adds the same apikey handling that exists in velocity_template.xml to all four copies of api_product_template.xml. Fixes: wso2/api-manager#4856 Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (4)
WalkthroughFour identical APIM module distribution files were updated to add API key authentication support in the Changes
Estimated Code Review Effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
ApiKeyMediatorconfiguration in their Velocity template (api_product_template.xml)x-api-keyfor AI APIs) to never be forwarded to backend services when accessed through an API Productapikeyhandling block that exists invelocity_template.xml(used for regular APIs) to all four copies ofapi_product_template.xmlRelated
Test plan
x-api-keyheader to backend"invalid x-api-key"(key sent, expected with dummy key)"invalid x-api-key"(key sent — was previously"x-api-key header is required")🤖 Generated with Claude Code
Summary by CodeRabbit