Skip to content

Adding info about when the firewall needs to encompass all pages #17444

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 23, 2024

Conversation

ThomasLandauer
Copy link
Contributor

Added benefit: This also makes clear right away, that if somebody has multiple ways to login, the solution is not multiple firewalls, but one firewall (and a chain user provider).

@carsonbot carsonbot added this to the 5.4 milestone Nov 19, 2022
@javiereguiluz javiereguiluz merged commit 4fc6fe7 into symfony:5.4 Jan 23, 2024
@javiereguiluz
Copy link
Member

Merged! Thanks Thomas.

@ThomasLandauer ThomasLandauer deleted the patch-14 branch January 23, 2024 19:45
are public). You'll learn how to restrict access to URLs, controllers or
are public). On the other hand, all pages that you want to be *aware* of a logged in
user have to be under the same firewall. So if you want to display a "You are logged in
as ..." message on every page, they all have to be included in the same firewall.
Copy link
Member

@xabbuh xabbuh Jan 24, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Technically you can have several firewalls sharing the same context (see https://symfony.com/doc/current/reference/configuration/security.html#firewall-context). But I am not sure if it's worth to reference that here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants