You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Starting with Symfony 2.8, we can easily throw an AuthenticationException in the Security subsystem with a custom error message thanks to the new CustomUserMessageAuthenticationException (see symfony/symfony#15882).
It must be made clear that the message configured here is likely to be shown to the user, so no sensitive information should be included in this message.
The text was updated successfully, but these errors were encountered:
Hi, i want to make my first contribution to symfony project so i'm looking for the easy pick issues. I wonder if this issue is related to "How to Build a Traditional Login Form" recipe from the security cookbook chapter:
Is it possible to show sensitive information just in dev environment and show a safe fixed message in prod?
Then it is always safe. It's only unsafe if you try to use other things, like maybe error.message - which could contain any information. But the messageKey is always safe.
weaverryan
added
hasPR
A Pull Request has already been submitted for this issue.
and removed
actionable
Clear and specific issues ready for anyone to take them.
good first issue
Ideal for your first contribution! (some Symfony experience may be required)
labels
Nov 27, 2015
…thenticationException (weaverryan)
This PR was merged into the 2.8 branch.
Discussion
----------
Updating some places to use the new CustomUserMessageAuthenticationException
| Q | A
| ------------- | ---
| Doc fix? | no
| New docs? | yes
| Applies to | 2.8+
| Fixed tickets | #5736
Commits
-------
3d67202 tweaks thanks to the guys
1eb5f23 Updating some places to use the new CustomUserMessageAuthenticationException
Starting with Symfony 2.8, we can easily throw an
AuthenticationException
in the Security subsystem with a custom error message thanks to the newCustomUserMessageAuthenticationException
(see symfony/symfony#15882).It must be made clear that the message configured here is likely to be shown to the user, so no sensitive information should be included in this message.
The text was updated successfully, but these errors were encountered: