Skip to content

Commit 0e2101b

Browse files
Update text deprecated
1 parent 67c89f2 commit 0e2101b

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

security/custom_authenticator.rst

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -132,9 +132,9 @@ The authenticator can be enabled using the ``custom_authenticators`` setting:
132132
133133
.. deprecated:: 5.4
134134

135-
Having multiple user providers and a ``custom_authenticator`` and not having specified the user provider
136-
to use has been deprecated in Symfony 5.4. If you have registered multiple user providers, you must set the
137-
``provider`` key to one of the configured providers, even if your custom authenticators don't use it.
135+
If you have registered multiple user providers, you must set the
136+
``provider`` key to one of the configured providers, even if your
137+
custom authenticators don't use it. Not doing so is deprecated in Symfony 5.4.
138138

139139
.. versionadded:: 5.2
140140

@@ -191,7 +191,7 @@ can define what happens in these cases:
191191
If your login method is interactive, which means that the user actively
192192
logged into your application, you may want your authenticator to implement the
193193
:class:`Symfony\\Component\\Security\\Http\\Authenticator\\InteractiveAuthenticatorInterface`
194-
so that it dispatches an
194+
so that it dispatches an
195195
:class:`Symfony\\Component\\Security\\Http\\Event\\InteractiveLoginEvent`
196196

197197
.. _security-passport:

0 commit comments

Comments
 (0)