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 a14bd07

Browse filesBrowse files
author
Kevin Weber
committed
Security - Authentication - removed inaccurate tip.
1 parent 5bdfd71 commit a14bd07
Copy full SHA for a14bd07

File tree

Expand file treeCollapse file tree

1 file changed

+5
-9
lines changed
Filter options
Expand file treeCollapse file tree

1 file changed

+5
-9
lines changed

‎components/security/authentication.rst

Copy file name to clipboardExpand all lines: components/security/authentication.rst
+5-9Lines changed: 5 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -285,15 +285,11 @@ Authentication Success and Failure Events
285285
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
286286

287287
When a provider authenticates the user, a ``security.authentication.success``
288-
event is dispatched. Likewise, when no providers authenticate the user,
289-
a ``security.authentication.failure`` event is dispatched. You
290-
could listen on the ``security.authentication.failure`` event, for example,
291-
in order to log failed login attempts.
292-
293-
.. tip::
294-
295-
One of the authentication events is always triggered when a request points
296-
to a secured area.
288+
event is dispatched. Likewise, when a provider attempts authentication but
289+
fails (i.e. throws an ``AuthenticationException``), a
290+
``security.authentication.failure`` event is dispatched. You could listen on
291+
the ``security.authentication.failure`` event, for example, in order to log
292+
failed login attempts.
297293

298294
Security Events
299295
~~~~~~~~~~~~~~~

0 commit comments

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