I was about to remove 2FA for each user using: sudo gitlab-rake gitlab:two_factor:disable_for_all_users but i was pretty sure that would fail due to the enforcement. I was stuck on the activation page with invalid pin code. signed-in again on my gitlab instance, after the grace period of 48h to activate 2FA & bam.i did not activated root’s 2FA because i was waiting for a bitwarden deployment.added 2FA for root and few hours after desactivated it.I am pretty sure this is a bug on gitlab-side.
I searched online and the only same issue i’ve found was yours You were everywhere: stackoverflow, server fault and here, on gitlab. If its failing at the system or instance-level, I’d expect to see some relevant errors in the logs that we can use to troubleshoot further. An easy way to do this would be to run sudo gitlab-ctl tail on the GitLab server and then duplicating the problem by entering your OTP pin code and clicking “Register”.
If other users are experiencing this same problem on your GitLab server, or if switching to using a different OTP app doesn’t work, I suggest checking the logs for any relevant error messages. If we can get it registered with a different App, this indicates there’s not a problem registering 2FA on server, but there’s likely a problem with your OTP app. andOTP: feature rich open source app for Android which supports PGP encrypted backups.Google Authenticator: proprietary app for iOS and Android.Authenticator: open source app for iOS devices.To verify or rule out the possibility that the problem is isolated to your OTP app, can you try to register using a different OTP Authenticator App? If so, I suspect this problem might be related to your one time password authenticator app. Do you know if there any other users on this private GitLab CE instance having this problem?
0 kommentar(er)
