| Age | Commit message (Collapse) | Author |
|---|
|
|
|
This spec would start to fail on the first of the month because the
generated text would have a zero-padded day (e.g. 01 vs 1), whereas the
expected text check used an unpadded day via the `-d` parameter in
strftime (https://apidock.com/ruby/Date/strftime). To fix this, we
use use the `d` parameter to pad zeros.
This spec was introduced recently in
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/25731.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/59731
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This prevents a redirect loop when a user has to enable 2FA and accept
the terms.
Now they will need to accept the terms, then enable 2FA, or any other requirements.
|
|
This enforces the terms in the web application. These cases are
specced:
- Logging in: When terms are enforced, and a user logs in that has not
accepted the terms, they are presented with the screen. They get
directed to their customized root path afterwards.
- Signing up: After signing up, the first screen the user is presented
with the screen to accept the terms. After they accept they are
directed to the dashboard.
- While a session is active:
- For a GET: The user will be directed to the terms page first,
after they accept the terms, they will be directed to the page
they were going to
- For any other request: They are directed to the terms, after they
accept the terms, they are directed back to the page they came
from to retry the request. Any information entered would be
persisted in localstorage and available on the page.
|
|
|
|
Ensure that OTP backup codes are always invalidated - 10.5 port
See merge request gitlab/gitlabhq!2324
|
|
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
