@@ -123,16 +123,18 @@ Upgrade the Password
123123Upon successful login, the Security system checks whether a better algorithm
124124is available to hash the user's password. If it is, it'll hash the correct
125125password using the new hash. If you use a Guard authenticator, you first need to
126- `provide the original password to the Security system <Provide the Password when using Guard >`_ .
126+ :ref: `provide the original password to the Security system <provide- the-password-guard >` .
127127
128128You can enable the upgrade behavior by implementing how this newly hashed
129129password should be stored:
130130
131- * `When using Doctrine's entity user provider <Upgrade the Password when using Doctrine >`_
132- * `When using a custom user provider <Upgrade the Password when using a custom User Provider >`_
131+ * :ref: `When using Doctrine's entity user provider <upgrade- the-password-doctrine >`
132+ * :ref: `When using a custom user provider <upgrade- the-password- custom-provider >`
133133
134134After this, you're done and passwords are always hashed as secure as possible!
135135
136+ .. _provide-the-password-guard :
137+
136138Provide the Password when using Guard
137139~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
138140
@@ -157,6 +159,8 @@ for this login request. This password is used in the migration process::
157159 }
158160 }
159161
162+ .. _upgrade-the-password-doctrine :
163+
160164Upgrade the Password when using Doctrine
161165~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
162166
@@ -186,6 +190,8 @@ storing the newly created password hash::
186190 }
187191 }
188192
193+ .. _upgrade-the-password-custom-provider :
194+
189195Upgrade the Password when using a Custom User Provider
190196~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
191197
0 commit comments