8000 Firewall - add info which firewall and acl has been hit · Issue #4753 · symfony/symfony · GitHub
[go: up one dir, main page]

Skip to content

Firewall - add info which firewall and acl has been hit #4753

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

Closed
devhelp opened this issue Jul 4, 2012 · 4 comments
Closed

Firewall - add info which firewall and acl has been hit #4753

devhelp opened this issue Jul 4, 2012 · 4 comments

Comments

@devhelp
Copy link
devhelp commented Jul 4, 2012

Could you add information in the debug toolbar which firewall has been hit during the request and which acl has been invoked ?
I am having a problem when debugging it and I think this will be helpfull during development.

@schmittjoh
Copy link
Contributor

In the meantime, you could install JMSDebuggingBundle to obtain that
information (at least the firewall part).

On Wed, Jul 4, 2012 at 10:21 PM, devhelp <
reply@reply.github.com

wrote:

Could you add information in the debug toolbar which firewall has been hit
during the request and which acl has been invoked ?
I am having a problem when debugging it and I think this will be helpfull
during development.


Reply to this email directly or view it on GitHub:
#4753

@devhelp
Copy link
Author
devhelp commented Jul 7, 2012

Thanks for the tip, I wasn't aware of that

@lsmith77
Copy link
Contributor

shouldn't be too hard to add this @devhelp .. maybe take a stab at doing this?

@javiereguiluz
Copy link
Member

I've tried to fix this and show the firewall name in the toolbar. Sadly I couldn't. Getting the providerKey is easy, but sometimes it's different from the firewall name. Getting the real firewall name is "impossible" (in this comment you can see the code some people use to get it).

I would close this as "won't fix".

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

No branches or pull requests

4 participants
0