security: let database permissions override code-level AllowAnonymous#4646
security: let database permissions override code-level AllowAnonymous#4646ktsapo wants to merge 1 commit intoshesha-io:releases/0.43from
Conversation
Code-level [AllowAnonymous] attributes completely bypassed database-configured permissions. Modify the authorization pipeline so database configuration takes precedence. If a DB record has an explicit access level, it overrides the code attribute. If no DB override exists, the code attribute is still respected. Closes shesha-io#4621 Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
Warning Rate limit exceeded
⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
📝 Coding Plan
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
IAllowAnonymousinSheshaAuthorizationFilterso authorization helpers always runApiAuthorizationHelper, instead of returning early for[AllowAnonymous]attributes, passAllowAnonymousas thereplaceInheritedfallbackTest plan
[AllowAnonymous]and no DB override still work anonymously[AllowAnonymous]but a DB override ofRequiresPermissionsrequire the configured permission[AllowAnonymous]but a DB override ofDisablereturn 404Closes #4621
🤖 Generated with Claude Code