Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork9.7k
[Security] Don't allow empty username or empty password#46109
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
chalasr commentedApr 19, 2022
Thanks for contributing to Symfony! |
…d (bikalbasnet)This PR was squashed before being merged into the 6.2 branch.Discussion----------[Security] Don't allow empty username or empty password| Q | A| ------------- | ---| Branch? | 6.2| Bug fix? | no| New feature? | yes| Deprecations? | yes| Tickets |#46100| License | MIT| Doc PR | -<!--Replace this notice by a short README for your feature/bugfix.This will help reviewers and should be a good start for the documentation.Additionally (seehttps://symfony.com/releases): - Always add tests and ensure they pass. - Bug fixes must be submitted against the lowest maintained branch where they apply (lowest branches are regularly merged to upper ones so they get the fixes too.) - Features and deprecations must be submitted against the latest branch. - Changelog entry should followhttps://symfony.com/doc/current/contributing/code/conventions.html#writing-a-changelog-entry - Never break backward compatibility (seehttps://symfony.com/bc).-->Reopened from#46109 into `6.1` branch as this is not a bug rather a security featureCommits-------db5afbd [Security] Don't allow empty username or empty password
First time PR on Symfony. So apologies for any mistake.
As I understand if I merge on 5.4, it will be merged to 6.0 and other higher version, let me know if I need to open PR in multiple branch.