Skip to content

Commit 717c135

Browse files
committed
minor #11457 #21571 updated "Authentication Success and Failure Events" section (oleg-andreyev)
This PR was merged into the 4.4 branch. Discussion ---------- #21571 updated "Authentication Success and Failure Events" section Updated "Authentication Success and Failure Events" `security.authentication.success` can be dispatched in the following cases: - if `always_authenticate_before_granting` is enabled and `isGranted` is called - if a token is not authenticated before `AccessListener` is invoked - if customer submitted credentials (actual authentication) symfony/symfony#21571 Commits ------- dc91bfd #21571 updated "Authentication Success and Failure Events" section
2 parents a7c6662 + dc91bfd commit 717c135

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

components/security/authentication.rst

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -290,9 +290,9 @@ Authentication Success and Failure Events
290290
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
291291

292292
When a provider authenticates the user, a ``security.authentication.success``
293-
event is dispatched. But beware - this event will fire, for example, on *every*
294-
request if you have session-based authentication. See ``security.interactive_login``
295-
below if you need to do something when a user *actually* logs in.
293+
event is dispatched. But beware - this event may fire, for example, on *every*
294+
request if you have session-based authentication, if ``always_authenticate_before_granting`` is enabled or if token is not authenticated before AccessListener is invoked.
295+
See ``security.interactive_login`` below if you need to do something when a user *actually* logs in.
296296

297297
When a provider attempts authentication but fails (i.e. throws an ``AuthenticationException``),
298298
a ``security.authentication.failure`` event is dispatched. You could listen on

0 commit comments

Comments
 (0)