@@ -127,16 +127,18 @@ Upgrade the Password
127127Upon successful login, the Security system checks whether a better algorithm
128128is available to hash the user's password. If it is, it'll hash the correct
129129password using the new hash. If you use a Guard authenticator, you first need to
130- :ref: `provide the original password to the Security system <Provide the Password when using Guard >`.
130+ :ref: `provide the original password to the Security system <provide- the-password-guard >`.
131131
132132You can enable the upgrade behavior by implementing how this newly hashed
133133password should be stored:
134134
135- * :ref: `When using Doctrine's entity user provider <Upgrade the Password when using Doctrine >`
136- * :ref: `When using a custom user provider <Upgrade the Password when using a Custom User Provider >`
135+ * :ref: `When using Doctrine's entity user provider <upgrade- the-password-doctrine >`
136+ * :ref: `When using a custom user provider <upgrade- the-password-custom-provider >`
137137
138138After this, you're done and passwords are always hashed as secure as possible!
139139
140+ .. _provide-the-password-guard :
141+
140142Provide the Password when using Guard
141143~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
142144
@@ -161,6 +163,8 @@ for this login request. This password is used in the migration process::
161163 }
162164 }
163165
166+ .. _upgrade-the-password-doctrine :
167+
164168Upgrade the Password when using Doctrine
165169~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
166170
@@ -190,6 +194,8 @@ storing the newly created password hash::
190194 }
191195 }
192196
197+ .. _upgrade-the-password-custom-provider :
198+
193199Upgrade the Password when using a Custom User Provider
194200~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
195201
0 commit comments