Implement FilamentUser on the User model#390
Merged
Merged
Conversation
Filament 5.6 now denies panel access with a 403 outside the local environment when the authenticated user model does not implement the FilamentUser contract. Implement it with the existing semantics: any authenticated user may access the dashboard. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0157S7dDNDwYuqWsqeg1DB94
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Filament 5.6 denies panel access with a 403 outside the
localenvironment when the authenticated user model does not implement theFilamentUsercontract (Filament\Http\Middleware\Authenticate).Cachet\Models\Userdoesn't implement it, so any production install that updates to Filament ≥ 5.6 loses access to the dashboard entirely.The test suite doesn't catch this because Testbench's workbench skeleton runs with
APP_ENV=local, where Filament skips the check.What changed
Cachet\Models\Usernow implementsFilament\Models\Contracts\FilamentUser, withcanAccessPanel()returningtrue— preserving the existing semantics where any authenticated user may access the dashboard.Split out of #389 (the MCP server PR), where it originally landed; it's independent of MCP and worth releasing on its own.
🤖 Generated with Claude Code
https://claude.ai/code/session_0157S7dDNDwYuqWsqeg1DB94