2FA not working post upgrading to 13.2.8
Hi All,
Post upgrading Gitlab to 13.2.8 the Two factor authentication is not working and not logging any error too. The below error recieved in GUI but no error in logs even tried to track via gitlab-ctl tail but no luck.
Designs
- Show closed items
Activity
-
Newest first Oldest first
-
Show all activity Show comments only Show history only
- Ansar changed title from 2AF not working post upgrading to 3.2.8 to 2FA not working post upgrading to 3.2.8
changed title from 2AF not working post upgrading to 3.2.8 to 2FA not working post upgrading to 3.2.8
- Ansar changed title from 2FA not working post upgrading to 3.2.8 to 2FA not working post upgrading to 13.2.8
changed title from 2FA not working post upgrading to 3.2.8 to 2FA not working post upgrading to 13.2.8
- Ansar changed the description
changed the description
- Maintainer
Thanks for submitting this issue. Since GitLab's development now happens in a single codebase, the canonical GitLab issue tracker is now at https://gitlab.com/gitlab-org/gitlab/issues.
This issue will automatically be moved there.
- 🤖 GitLab Bot 🤖 added automation:to-be-locked in GitLab FOSS label
added automation:to-be-locked in GitLab FOSS label
- 🤖 GitLab Bot 🤖 moved from gitlab-foss#79550 (moved)
moved from gitlab-foss#79550 (moved)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#903 (closed)
mentioned in issue gitlab-org/quality/triage-reports#903 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#907 (closed)
mentioned in issue gitlab-org/quality/triage-reports#907 (closed)
Hi All,
I am using 13.2.6 and facing the same issue. any workaround or fix for this issue ?
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#992 (closed)
mentioned in issue gitlab-org/quality/triage-reports#992 (closed)
- 🤖 GitLab Bot 🤖 added sectiondev label
added sectiondev label
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#1051 (closed)
mentioned in issue gitlab-org/quality/triage-reports#1051 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#1105 (closed)
mentioned in issue gitlab-org/quality/triage-reports#1105 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#1198 (closed)
mentioned in issue gitlab-org/quality/triage-reports#1198 (closed)
- Ansar changed the description
Compare with previous version changed the description
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#1273 (closed)
mentioned in issue gitlab-org/quality/triage-reports#1273 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#1369 (closed)
mentioned in issue gitlab-org/quality/triage-reports#1369 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#1436 (closed)
mentioned in issue gitlab-org/quality/triage-reports#1436 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#1527 (closed)
mentioned in issue gitlab-org/quality/triage-reports#1527 (closed)
- 🤖 GitLab Bot 🤖 added vintage label
added vintage label
- Maintainer
Hi @Ansm
,Thanks for raising this bug.
Contributions like this are vital to help make GitLab a better product.
We would be grateful for your help in verifying whether your bug report requires further attention from the team. If you think this bug still exists, and is reproducible with the latest stable version of GitLab, please comment on this issue.
This issue has been inactive for more than 12 months now and based on the policy for inactive bugs, will be closed in 7 days.
Thanks for your contributions to make GitLab better!
- 🤖 GitLab Bot 🤖 added stale label
added stale label
- Maintainer
Hi @Ansm
,Based on the policy for inactive bugs, this issue is now being closed.
If you think this bug still exists, and is reproducible with the latest stable version of GitLab, please reopen this issue.
Thanks for your contributions to make GitLab better!
- 🤖 GitLab Bot 🤖 closed
closed
- 🤖 GitLab Bot 🤖 added auto closed label
added auto closed label