Google Token does not match generated token (clock is accurate)

I am running meteor app on Windows 10 with speakasy installed. time.is reports:

Your time is exact!The difference from Time.is was -0.039 seconds (±0.013 seconds).

However the tokens do not match - at all.

This is my code:

    verifyToken() {
        var myToken = this.state.authCode.trim()

        let currentValidToken = speakeasy.totp({ secret: this.secretBase32, encoding: 'base32' });
        let verified = speakeasy.time.verify({ 
            secret: this.secretBase32, 
            encoding: 'base32', 
            token: myToken
        })

        console.log(`mySecret = [${this.secretBase32}] CVT = [${currentValidToken}] MYTOKEN = ${myToken} VERIFIED= [${verified}]`);

        if (!verified) {

            return swal({
                title: "Invalid Code",
                text: "You have 2 more attempts.",
                showConfirmButton: true,
                type: "error"
            });
        } else {

            return swal({
                title: "Jackpot!",
                text: "You da man.",
                showConfirmButton: true,
                type: "success"
            });
        }
    }

[MercenaryUSA]

I am having this same issue. I’ve verified that the clock is accurate, I’m using base32 for the secret and it’s a multiple of 8, but Google Authenticator is still generating a separate code from speakeasy.

Has anyone found a solution for this?

Never mind, I got it working. It was simply an error in my code that I didn’t realize. That’s what happens when you stay up for over 12 hours and are coding at 3am.

[markbao]

Thanks for checking those. So the JS code is running on the client? The package doesn’t support (as in, it hasn’t been tested) usage on the client side - it’s exclusively for server side use. Do try to see if it works on the server and let me know what you find.