Fix: Address User-Controlled Data Risk in isAuthenticated() #27562
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.
Related to #27051
For enhancing application security, this PR modifies the
isAuthenticated()
endpoint to return a boolean indicating the authentication status instead of a potentially user-controlled value (principal.getName()). This change mitigates the risk of reflecting user-controlled data and strengthens the security of the application.Please make sure the below checklist is followed for Pull Requests.
If the PR is not ready for review, please consider converting it to a Draft. You can also add the
skip-ci
label to prevent CI build on branch.