fix(docs): honest auth model + version metadata sync - #22
Conversation
…unts README's Authentication section now states plainly that authorization is enforced by IWS in front of the plugin (no in-plugin check exists) and warns against exposing IWS unauthenticated. pyproject version now tracks Info.plist's YYYY.R.P scheme. Stale test/tool counts refreshed. Closes #20, closes #21. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EYAGXd4bE9D9Z5kZeSHeo7
📝 WalkthroughWalkthroughThe PR clarifies that IWS enforces authentication, updates documented MCP and test counts, and aligns project and plugin versions at ChangesDocumentation and release metadata alignment
Estimated code review effort: 1 (Trivial) | ~5 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ 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 |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@README.md`:
- Line 39: Update the authentication description in the README to state that the
plugin does not validate or use credentials, rather than claiming it never sees
them. Preserve the explanation that IWS enforces authentication before invoking
the MCP endpoint.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: b3ba2de6-34b2-4b71-94a1-c93425a3e254
📒 Files selected for processing (4)
CLAUDE.mdIndigo MCP Lite.indigoPlugin/Contents/Info.plistREADME.mdpyproject.toml
| ### Authentication | ||
|
|
||
| All MCP requests require a Bearer token. Use either: | ||
| Authentication is enforced by **Indigo's Web Server (IWS), in front of the plugin** — the plugin itself performs no Authorization check and never sees your credentials. Requests without a valid Bearer token are rejected by IWS before the MCP endpoint is invoked. Use either: |
There was a problem hiding this comment.
🔒 Security & Privacy | 🟠 Major | ⚡ Quick win
Do not claim the plugin “never sees” credentials.
plugin.py forwards the complete headers dictionary to mcp_handler.handle_request, which passes normalized headers into _dispatch. The plugin does not validate Authorization, but it does receive the header. Change this to “does not validate or use your credentials” to preserve the intended IWS boundary without misstating the data flow.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@README.md` at line 39, Update the authentication description in the README to
state that the plugin does not validate or use credentials, rather than claiming
it never sees them. Preserve the explanation that IWS enforces authentication
before invoking the MCP endpoint.
Closes #20, closes #21.
🤖 Generated with Claude Code
https://claude.ai/code/session_01EYAGXd4bE9D9Z5kZeSHeo7
Summary by CodeRabbit
Documentation
Chores