@ogizanagi is right about that use cases are limited but I would say it's still good to have in the documentation because of the considerable number of existing support questions and issues for which a small mention about this feature would have been useful:

http://stackoverflow.com/questions/19610316/how-to-access-firewall-configuration-in-controller
http://stackoverflow.com/questions/17886818/symfony2-detect-if-user-is-inside-a-secure-firewall
http://stackoverflow.com/questions/23128399/symfony2-get-firewall-name-on-login-page
Retrieve the current firewall name for a Request symfony#14435
[DX][Security] Introduce a class representing a/the current firewall symfony#15294
Firewall - add info which firewall and acl has been hit symfony#4753

Even if it's just about documenting what is actually possible to do on this subject so it would be clear what is not, and give the right way to do (especially since using the security token providerKey is neither always available nor always accurate).

Maybe we could start by adding a small mention in the bundle documentation and make it grows as we improve the feature (I feel it could be useful to add some more informations about the registered listeners for instance, but let's wait for concrete use cases).

If nobody pick it I can give it a try asap

Uh oh!

Add docs for the Firewall Config class #7164

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions