@@ -127,18 +127,16 @@ Upgrade the Password
127
127
Upon successful login, the Security system checks whether a better algorithm
128
128
is available to hash the user's password. If it is, it'll hash the correct
129
129
password 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 when using Guard >`.
131
131
132
132
You can enable the upgrade behavior by implementing how this newly hashed
133
133
password should be stored:
134
134
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 when using Doctrine >`
136
+ * :ref: `When using a custom user provider <Upgrade the Password when using a Custom User Provider >`
137
137
138
138
After this, you're done and passwords are always hashed as secure as possible!
139
139
140
- .. _provide-the-password-when-using-guard :
141
-
142
140
Provide the Password when using Guard
143
141
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
144
142
@@ -163,8 +161,6 @@ for this login request. This password is used in the migration process::
163
161
}
164
162
}
165
163
166
- .. _upgrade-the-password-when-using-doctrine :
167
-
168
164
Upgrade the Password when using Doctrine
169
165
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
170
166
@@ -194,8 +190,6 @@ storing the newly created password hash::
194
190
}
195
191
}
196
192
197
- .. _upgrade-the-password-when-using-a-custom-user-provider :
198
-
199
193
Upgrade the Password when using a Custom User Provider
200
194
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
201
195
0 commit comments