7179fbab77
Invited users were allowed to accept invites without entering a password. When this happened, instead of receiving an activation email, they received a password reset email. Basically, a user could postpone choosing a password until after registration. Unfortunately, this led to a confusing user experience and this commit attempts to fix that by making the client require a password. There is a single case when users do not need to input a password: when they sign up using an external authenticator and password field is completely hidden. In this case, the third party handles the password logic. Technically, invites can still be redeemed without a password, but that functionality was kept to preserve backwards compatibility. |
||
|---|---|---|
| .. | ||
| assets | ||
| controllers | ||
| helpers | ||
| jobs | ||
| mailers | ||
| models | ||
| serializers | ||
| services | ||
| views | ||