Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Commit b39e369

Browse filesBrowse files
committed
Small extra clarification that security.authentication.success is probably
*not* the event you're looking for
1 parent b22637c commit b39e369
Copy full SHA for b39e369

File tree

Expand file treeCollapse file tree

1 file changed

+6
-3
lines changed
Filter options
Expand file treeCollapse file tree

1 file changed

+6
-3
lines changed

‎components/security/authentication.rst

Copy file name to clipboardExpand all lines: components/security/authentication.rst
+6-3Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -286,9 +286,12 @@ Authentication Success and Failure Events
286286
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
287287

288288
When a provider authenticates the user, a ``security.authentication.success``
289-
event is dispatched. Likewise, when a provider attempts authentication but
290-
fails (i.e. throws an ``AuthenticationException``), a
291-
``security.authentication.failure`` event is dispatched. You could listen on
289+
event is dispatched. But beware - this event will fire, for example, on *every*
290+
request if you have session-based authentication. See ``security.interactive_login``
291+
below if you need to do something when a user *actually* logs in.
292+
293+
When a provider attempts authentication but fails (i.e. throws an ``AuthenticationException``),
294+
a ``security.authentication.failure`` event is dispatched. You could listen on
292295
the ``security.authentication.failure`` event, for example, in order to log
293296
failed login attempts.
294297

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.