1password as 2FA authenticator does not work in zimbra

Options

I like 1password as 2FA authenticator because of autofill and centralization of secrets.

However, zimbra (on-prem email) can verify 2FA from authy and Keepass but not from 1password.


1Password Version: 7.7.810
Extension Version: Not Provided
OS Version: Windows 10
Sync Type: Not Provided

Comments

  • nicosmaris
    nicosmaris
    Community Member
    Options

    So I was stuck at the step "Testing a new Web Browser session in a new Computer": https://wiki.zimbra.com/wiki/Zimbra_Two-factor_authentication

  • ag_ana
    ag_ana
    1Password Alumni
    Options

    Hi @nicosmaris!

    Does the authenticator code match between Authy and 1Password, for example, at any given time?

  • nicosmaris
    nicosmaris
    Community Member
    Options

    Each time I had setup 2FA from scratch.

    I opened the issue also at zimbra in case it is on their side. https://bugzilla.zimbra.com/show_bug.cgi?id=109371

  • ag_yaron
    ag_yaron
    1Password Alumni
    Options

    Hey @nicosmaris ,

    2FA codes are highly dependent on your computer's/device's clock being accurate. I assume that you use 1Password on your computer when you need to log into that website, but only 2FA codes generated in Authy on your mobile phone work. Does that sound like it might be the case here?

    If so, please check your computer's clock and make sure it is accurate. You can compare it to your mobile phone's clock or by just opening this clock here: https://time.is/

  • nicosmaris
    nicosmaris
    Community Member
    Options

    Indeed, Android says "Your clock is 0.3 seconds behind" whereas Windows say 52.8.

  • ag_yaron
    ag_yaron
    1Password Alumni
    Options

    In that case, your Android should generate correct 2FA codes while Windows might not (though less than one minute should still work on most websites).

    Please try adjusting your Clock in Windows or better yet, have it synced automatically to Windows' server and see if 2FA codes are working properly now.

This discussion has been closed.