Remove more deprecations in 6.0 branch

Author: javiereguiluz

_build/redirection_map

@@ -517,3 +517,5 @@
 /security/named_encoders /security/named_hashers
 /components/inflector /components/string#inflector
 /security/experimental_authenticators /security/authenticator_manager
+/security/guard_authentication /security/authenticator_manager
+/security/multiple_guard_authenticators /security/authenticator_manager

cache.rst

@@ -99,7 +99,6 @@ The Cache component comes with a series of adapters pre-configured:
 
 * :doc:`cache.adapter.apcu </components/cache/adapters/apcu_adapter>`
 * :doc:`cache.adapter.array </components/cache/adapters/array_cache_adapter>`
-* :doc:`cache.adapter.doctrine </components/cache/adapters/doctrine_adapter>`
 * :doc:`cache.adapter.filesystem </components/cache/adapters/filesystem_adapter>`
 * :doc:`cache.adapter.memcached </components/cache/adapters/memcached_adapter>`
 * :doc:`cache.adapter.pdo </components/cache/adapters/pdo_doctrine_dbal_adapter>`
@@ -119,8 +118,6 @@ will create pools with service IDs that follow the pattern ``cache.[type]``.
             cache:
                 directory: '%kernel.cache_dir%/pools' # Only used with cache.adapter.filesystem
 
-                # service: cache.doctrine
-                default_doctrine_provider: 'app.doctrine_cache'
                 # service: cache.psr6
                 default_psr6_provider: 'app.my_psr6_service'
                 # service: cache.redis
@@ -144,15 +141,13 @@ will create pools with service IDs that follow the pattern ``cache.[type]``.
 
             <framework:config>
                 <!--
-                default_doctrine_provider: Service: cache.doctrine
                 default_psr6_provider: Service: cache.psr6
                 default_redis_provider: Service: cache.redis
                 default_memcached_provider: Service: cache.memcached
                 default_pdo_provider: Service: cache.pdo
                 -->
                 <!-- "directory" attribute is only used with cache.adapter.filesystem -->
                 <framework:cache directory="%kernel.cache_dir%/pools"
-                    default_doctrine_provider="app.doctrine_cache"
                     default_psr6_provider="app.my_psr6_service"
                     default_redis_provider="redis://localhost"
                     default_memcached_provider="memcached://localhost"
@@ -170,8 +165,6 @@ will create pools with service IDs that follow the pattern ``cache.[type]``.
             $framework->cache()
                 // Only used with cache.adapter.filesystem
                 ->directory('%kernel.cache_dir%/pools')
-                // Service: cache.doctrine
-                ->defaultDoctrineProvider('app.doctrine_cache')
                 // Service: cache.psr6
                 ->defaultPsr6Provider('app.my_psr6_service')
                 // Service: cache.redis
@@ -183,11 +176,6 @@ will create pools with service IDs that follow the pattern ``cache.[type]``.
             ;
         };
 
-.. deprecated:: 5.4
-
-    The ``default_doctrine_provider`` option was deprecated in Symfony 5.4 and
-    it will be removed in Symfony 6.0.
-
 .. _cache-create-pools:
 
 Creating Custom (Namespaced) Pools

components/cache/adapters/doctrine_adapter.rst

@@ -34,14 +34,4 @@ third parameters::
         $defaultLifetime = 0
     );
 
-.. tip::
-
-    A :class:`Symfony\\Component\\Cache\\DoctrineProvider` class is also provided by the
-    component to use any PSR6-compatible implementations with Doctrine-compatible classes.
-
-    .. deprecated:: 5.4
-
-        The ``DoctrineProvider`` class was deprecated in Symfony 5.4 and it will
-        be removed in Symfony 6.0.
-
 .. _`Doctrine Cache`: https://github.com/doctrine/cache

components/security/authentication.rst

@@ -296,14 +296,9 @@ Authentication Success and Failure Events
 
 When a provider authenticates the user, a ``security.authentication.success``
 event is dispatched. But beware - this event may fire, for example, on *every*
-request if you have session-based authentication, if ``always_authenticate_before_granting``
-is enabled or if token is not authenticated before AccessListener is invoked.
-See ``security.interactive_login`` below if you need to do something when a user *actually* logs in.
-
-.. deprecated:: 5.4
-
-    The ``always_authenticate_before_granting`` option was deprecated in
-    Symfony 5.4 and it will be removed in Symfony 6.0.
+request if you have session-based authentication, if token is not authenticated
+before AccessListener is invoked. See ``security.interactive_login`` below if
+you need to do something when a user *actually* logs in.
 
 When a provider attempts authentication but fails (i.e. throws an ``AuthenticationException``),
 a ``security.authentication.failure`` event is dispatched. You could listen on

reference/configuration/framework.rst

@@ -2710,12 +2710,6 @@ file
     Use the filesystem to cache annotations
 none
     Disable the caching of annotations
-a service id
-    A service id referencing a `Doctrine Cache`_ implementation
-
-.. deprecated:: 5.3
-
-    Using a service ID as the value of ``cache`` is deprecated since Symfony 5.3.
 
 file_cache_dir
 ..............
@@ -3510,7 +3504,6 @@ to know their differences.
 
 .. _`HTTP Host header attacks`: https://www.skeletonscribe.net/2013/05/practical-http-host-header-attacks.html
 .. _`Security Advisory Blog post`: https://symfony.com/blog/security-releases-symfony-2-0-24-2-1-12-2-2-5-and-2-3-3-released#cve-2013-4752-request-gethost-poisoning
-.. _`Doctrine Cache`: https://www.doctrine-project.org/projects/doctrine-cache/en/current/index.html
 .. _`egulias/email-validator`: https://github.com/egulias/EmailValidator
 .. _`RFC 5322`: https://tools.ietf.org/html/rfc5322
 .. _`PhpStormProtocol`: https://github.com/aik099/PhpStormProtocol

reference/configuration/security.rst

@@ -28,7 +28,6 @@ Configuration
 **Basic Options**:
 
 * `access_denied_url`_
-* `always_authenticate_before_granting`_
 * `anonymous`_
 * `erase_credentials`_
 * `hide_user_not_found`_
@@ -53,20 +52,6 @@ access_denied_url
 Defines the URL where the user is redirected after a ``403`` HTTP error (unless
 you define a custom access deny handler). Example: ``/no-permission``
 
-always_authenticate_before_granting
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-**type**: ``boolean`` **default**: ``false``
-
-.. deprecated:: 5.4
-
-    The ``always_authenticate_before_granting`` option was deprecated in
-    Symfony 5.4 and it will be removed in Symfony 6.0.
-
-If ``true``, the user is asked to authenticate before each call to the
-``isGranted()`` method in services and controllers or ``is_granted()`` from
-templates.
-
 anonymous
 ~~~~~~~~~
 

reference/forms/types/options/help.rst.inc

@@ -19,7 +19,3 @@ rendered below the field::
             'help' => new TranslatableMessage('order.status', ['%order_id%' => $order->getId()], 'store'),
         ])
     ;
-
-.. versionadded:: 5.4
-
-    Support for passing ``TranslatableMessage`` objects was introduced in Symfony 5.4.

security.rst

@@ -452,18 +452,8 @@ you to control *every* part of the authentication process (see the next section)
 Guard Authenticators
 ~~~~~~~~~~~~~~~~~~~~
 
-.. deprecated:: 5.3
-
-    Guard authenticators are deprecated since Symfony 5.3 in favor of the
-    :doc:`new authenticator-based system </security/authenticator_manager>`.
-
-A Guard authenticator is a class that gives you *complete* control over your
-authentication process. There are many different ways to build an authenticator;
-here are a few common use-cases:
-
-* :doc:`/security/form_login_setup`
-* :doc:`/security/guard_authentication` – see this for the most detailed
-  description of authenticators and how they work
+Guard authenticators are deprecated in favor of the
+:doc:`new authenticator-based system </security/authenticator_manager>`.
 
 Limiting Login Attempts
 ~~~~~~~~~~~~~~~~~~~~~~~
@@ -1436,7 +1426,7 @@ Frequently Asked Questions
 **Can I have Multiple Firewalls?**
     Yes! But it's usually not necessary. Each firewall is like a separate security
     system. And so, unless you have *very* different authentication needs, one
-    firewall usually works well. With :doc:`Guard authentication </security/guard_authentication>`,
+    firewall usually works well. With the :doc:`authenticator-based security </security/authenticator_manager>`,
     you can create various, diverse ways of allowing authentication (e.g. form login,
     API key authentication and LDAP) all under the same firewall.
 
@@ -1479,7 +1469,6 @@ Authentication (Identifying/Logging in the User)
     security/form_login_setup
     security/reset_password
     security/json_login_setup
-    security/guard_authentication
     security/password_migration
     security/auth_providers
     security/user_provider
@@ -1488,7 +1477,6 @@ Authentication (Identifying/Logging in the User)
     security/impersonating_user
     security/user_checkers
     security/named_hashers
-    security/multiple_guard_authenticators
     security/firewall_restriction
     security/csrf
     security/custom_authentication_provider

security/authenticator_manager.rst

@@ -266,14 +266,6 @@ The authenticator-based system dropped support for these providers and
 introduced a new authenticator interface as a base for custom
 authentication methods.
 
-.. tip::
-
-    :doc:`Guard authenticators </security/guard_authentication>` are still
-    supported in the authenticator-based system. It is however recommended
-    to also update these when you're refactoring your application to the
-    new system. The new authenticator interface has many similarities with the
-    guard authenticator interface, making the rewrite easier.
-
 Authenticators should implement the
 :class:`Symfony\\Component\\Security\\Http\\Authenticator\\AuthenticatorInterface`.
 You can also extend

security/form_login_setup.rst

@@ -45,7 +45,7 @@ and your generated code may be slightly different:
     Support for login form authentication was added to ``make:auth`` in MakerBundle 1.8.
 
 This generates the following: 1) login/logout routes & controller, 2) a template that
-renders the login form, 3) a :doc:`Guard authenticator </security/guard_authentication>`
+renders the login form, 3) an :doc:`authenticator </security/authenticator_manager>`
 class that processes the login submit and 4) updates the main security config file.
 
 **Step 1.** The ``/login``/``/logout`` routes & controller::
@@ -405,9 +405,9 @@ you have:
 .. image:: /_images/security/symfony_loggedin_wdt.png
    :align: center
 
-The Guard authentication system is powerful, and you can customize your authenticator
+The authentication system is powerful, and you can customize your authenticator
 class to do whatever you need. To learn more about what the individual methods do,
-see :doc:`/security/guard_authentication`.
+see :doc:`/security/authenticator_manager`.
 
 Controlling Error Messages
 --------------------------