SEO: Spring Security role-based UI access: why protecting routes beats hiding elements - #1191
Open
MatthewHawkins wants to merge 1 commit into
Open
MatthewHawkins wants to merge 1 commit into
MatthewHawkins wants to merge 1 commit into
Conversation
…utes beats hiding elements
MatthewHawkins
requested review from
EHandtkeBasis,
bbrennanbasis,
gosteenBASIS,
hyyan and
laurenic0l
as code owners
October 2, 2026 14:23
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
1 participant
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.
Adds SEO blog post: "Spring Security role-based UI access: why protecting routes beats hiding elements"
spring-security-route-access-controlspring security role based ui javaPosition piece arguing the architectural distinction between template-conditional element hiding (
sec:authorize,th:if) and route-level access enforcement (@RolesAllowed,@RouteAccess). Core argument: template conditionals run at render time and shape the HTML output; route-level annotations intercept before any component is constructed. References webforJ's production hardening guide ("setVisible(false) is an interface cue, not access control") as the anchor. No code snippets — pure architectural argument. Links to/docs/security/annotations,/docs/security/spel-expressions, and/docs/security/application-security/production-hardening.🤖 Generated with Claude Code
https://claude.ai/code/session_014VeRNh5tCqKiuVVj6UfSjL
Generated by Claude Code