Skip to content

[Security] Replace message data in JSON security error response #39859

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

Conversation

wouterj
Copy link
Member

@wouterj wouterj commented Jan 16, 2021

Q A
Branch? 5.2
Bug fix? yes
New feature? no
Deprecations? no
Tickets Fix #39663
License MIT
Doc PR n/a

@wouterj wouterj requested a review from chalasr as a code owner January 16, 2021 15:40
@wouterj wouterj force-pushed the issue-39663/replace-message-data-in-security-exception branch from 13cdedb to 98b0373 Compare January 16, 2021 15:41
@wouterj wouterj force-pushed the issue-39663/replace-message-data-in-security-exception branch from 98b0373 to 5e5795a Compare January 16, 2021 22:33
@chalasr chalasr changed the base branch from 5.x to 5.2 January 16, 2021 23:05
@chalasr
Copy link
Member

chalasr commented Jan 16, 2021

Thank you Wouter.

@chalasr chalasr merged commit 5ba4925 into symfony:5.2 Jan 16, 2021
chalasr added a commit that referenced this pull request Jan 16, 2021
…ponse (wouterj)

This PR was merged into the 4.4 branch.

Discussion
----------

[Security] Replace message data in JSON security error response

| Q             | A
| ------------- | ---
| Branch?       | 4.4
| Bug fix?      | yes
| New feature?  | no
| Deprecations? | no
| Tickets       | Fix part of #39663
| License       | MIT
| Doc PR        | n/a

The 4.4 part of #39859

Commits
-------

ab2ca71 [Security] Replace message data in JSON security error response
@fabpot fabpot mentioned this pull request Jan 27, 2021
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.

[RateLimiter] [Security] Invalid error message when max login attempts has been reached
4 participants