Skip to content

Commit d4517d0

Browse files
committed
bug #11166 [Security] Fix stateless mention (tyx)
This PR was merged into the 4.2 branch. Discussion ---------- [Security] Fix stateless mention According to https://github.com/symfony/symfony/blob/5aa0967f9f0ab803ededefb040d48a0ebc7a27a6/src/Symfony/Component/Security/Guard/GuardAuthenticatorHandler.php#L43 Firewall of pure API should have `stateless` to `true` in fact <!-- If your pull request fixes a BUG, use the oldest maintained branch that contains the bug (see https://symfony.com/roadmap for the list of maintained branches). If your pull request documents a NEW FEATURE, use the same Symfony branch where the feature was introduced (and `master` for features of unreleased versions). --> Commits ------- 2283cd2 Fix stateless mention
2 parents caf796f + 2283cd2 commit d4517d0

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

security/user_provider.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -379,7 +379,7 @@ command will generate a nice skeleton to get you started::
379379
* called. Your job is to make sure the user's data is still fresh by,
380380
* for example, re-querying for fresh User data.
381381
*
382-
* If your firewall is "stateless: false" (for a pure API), this
382+
* If your firewall is "stateless: true" (for a pure API), this
383383
* method is not called.
384384
*
385385
* @return UserInterface

0 commit comments

Comments
 (0)