Bad Code error with new OTP

[hitenmandalia]

Steps to reproduce

1. Once install is complete, oAuth user see's Account in Construction. This is displayed even after leaving it for some time
2. Generate new OTP code for user.
3. When user logs in, and enters OTP, they see Bad Code error

Expected behaviour

OTP should be accepted

Actual behaviour

Bad Code error

Server configuration

Operating system: Alpine Linux

Web server: Nginx

Database: MySQL 8

PHP version:

Teampass version: 3.1.2.172

[hitenmandalia]

Tested with a locally created user and this is not an issue. so seems its only with oauth users?

[nilsteampassnet]

Have you checked what the apache log contains?

[hitenmandalia]

Hi @nilsteampassnet Checked and nothing appears in the logs. I just get bad code on screen. I have ensure that i have put in the code given when generating new keys but never work.

All AzureAD users are able to log in. However, they get the Account in Construction message, which never disappears. As reference by jhumphries in #4440 (second to last post), when trying to generate new keys and using them, it get the bad code error.

If i create the user locally in teampass, then I do not experience this issue.

[hitenmandalia]

so i just found something. It seems that the column "is_ready_for_usage" in the teampass_users table, for my oauth2 users stays at 0. I changed it to 1 and the Account in Construction has now disappeared.