Skip to content

Conversation

@nicolas-grekas
Copy link
Member

@nicolas-grekas nicolas-grekas commented Sep 4, 2025

Q A
Branch? 7.4
Bug fix? no
New feature? no
Deprecations? yes
Issues #42349
License MIT

Instead of #59232

Having the user FQCN in the remember-me cookie leaks internal details that are not needed.

In the end userProvider->loadUserByIdentifier() is called, so that there's not need to early-exclude a cookie that's otherwise valid - and that's the only practical use case.

…ails::getUserFqcn()` in order to remove the user FQCN from the remember-me cookie in 8.0
@fabpot
Copy link
Member

fabpot commented Sep 10, 2025

Thank you @nicolas-grekas.

@fabpot fabpot merged commit 236b078 into symfony:7.4 Sep 10, 2025
9 of 12 checks passed
@nicolas-grekas nicolas-grekas deleted the sec-rme-fqcn branch September 10, 2025 12:12
nicolas-grekas added a commit that referenced this pull request Sep 15, 2025
…tToken` and `RememberMeDetails` (xabbuh)

This PR was merged into the 7.4 branch.

Discussion
----------

[Security] deprecate the FQCN properties of `PersistentToken` and `RememberMeDetails`

| Q             | A
| ------------- | ---
| Branch?       | 7.4
| Bug fix?      | no
| New feature?  | no
| Deprecations? | yes
| Issues        |
| License       | MIT

while cleaning up the `8.0` branch from the deprecations introduced in #61654 I wondered if we shouldn't also deprecate passing the user FQCN to `PersistentToken` and `RememberMeDetails` in the first place

Commits
-------

0e733fd deprecate the FQCN properties of PersistentToken and RememberMeDetails
This was referenced Oct 27, 2025
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.

5 participants