Feature #1082
closed
Added by Mykola Romanov over 6 years ago.
Updated almost 6 years ago.
Description
please do the following:
1. make the confirmation screen look fine on the password retreival form
2. make it work on hit ENTER
3. if it didn`t work - display an error, and show a button to retreive again
4. while registering - do not show "registration ok" if move has returned you error 400
5. while activating the account, we may have the different errors. When Token expired - we should show a message "Активація вже неможлива. Або ви надто давно реєструвалися, або вже неуспішно намагалися активувати аккаунт. (Активация невозможна. Либо Вы слишком давно регистрировались, либо уже безуспешно пытались его активировать.)" And a link - "Надіслати нового листа активації"(Отправить новое письмо активации)
6. The link is sending the password retrieval email.
7. please, restrics everything BUT latin, numbers, and this &<>!#$%()*+,-./:;=?@[]^_{|}~§
8. the minimum length must change to 4 characters
9. no limits on Upper case, numbers or whatever should be applied
- Status changed from New to In Progress
- Assignee set to Mykola Romanov
Workload estimate is 4 days.
Waiting for your approval.
OK if we handle all MOVE errors properly
- Assignee changed from Mykola Romanov to Denys Bezuhlyi
point 7 implies that no cyrillic characters are allowed in the form.
however, i believe we are letting them through right now.
The error message for the password should be the following:
"Пароль должен содержать больше 4 знаков. Без кириллицы и редко используемых спецсимволов"
"Пароль має містити більше ніж 4 знаков. Без кирилиці та рідковживаних спецсимволів"
10. Please, add the button "show password".
It should act for both fields (password and confirmation) at a time.
This button should be present on each page with password
We approve the estimation
- Assignee changed from Denys Bezuhlyi to Yevgen Voronetskyy
- Assignee changed from Yevgen Voronetskyy to Mykola Romanov
- % Done changed from 0 to 80
@m.romanov We are out of budget for this task.
As we have to assist ADEO on testing the fox for password weakness, we need 2 additional days.
Waiting for your approval.
From Bruno's investigation:
a priori le problème ici c'est que le WAC calcule un score pour le mot de passe (en fonction du nombre et du type de
caractères) et il le compare à un paramètre "strength_score" qui n'est pas documenté
c'est ce paramètre qu'on a dû abaisser pour que le mot de passe soit accepté...
- Assignee changed from Mykola Romanov to Yevgen Voronetskyy
- % Done changed from 80 to 0
- Assignee changed from Yevgen Voronetskyy to Denys Bezuhlyi
- Assignee changed from Denys Bezuhlyi to Yevgen Voronetskyy
- Status changed from In Progress to Resolved
- Assignee changed from Yevgen Voronetskyy to Mykola Romanov
Done and deployed to prod. Please, confirm and close the ticket.
- Project changed from 20 to Old
- Status changed from Resolved to Closed
Also available in: Atom
PDF