Authentication failure with Chrome on Win10: The JWK "dp" member contained a leading zero

qbracken
qbracken
Community Member
in Business and Teams

When using Chrome on Windows 10 to log in to 1Password for Teams beta for the first time (where you are asked to provide both the Master Password and Account Key), the authentication will fail with the error message:

   Cannot sign in. The JWK "dp" member contained a leading zero.

Google Chrome version 48.0.2564.97 m
Windows OS version: 10.0.14257 Build 14257

1Password Version: N/A
Extension Version: N/A
OS Version: 10.0.14257 Build 14257
Sync Type: N/A
Referrer: forum-search:chrome jwk

Comments

  • rob
    rob

    Wow, that's super interesting, @qbracken. Thanks for the report! We'll have to look into this and see what we can find out.

    Have you tried it more than once and gotten the same error?

  • qbracken
    qbracken
    Community Member

    @rob, yes. It's 100% repeatable. I have not been able to access my team vault in Chrome.

  • Jacob
    Jacob
    edited February 2016

    @qbracken Thanks for letting us know. We discovered that this is a bug with Microsoft Edge, which is the browser you used to set up your account. We filed the bug with Microsoft and we'll be looking into a workaround, but in the meantime the only browser you'll be able to use with your account is Edge. Signing up with that caused the issue, but things should still work properly in that browser. You may be able to use Firefox as well. Please give it a try and let us know how that goes.

    If you'd like to use Chrome now, we can help you move your data out of 1Password for Teams and delete your account so you can set things up in Chrome.

    Thanks again for helping us identify this issue. :) We don't have a lot of users on Microsoft Edge, so we really appreciate it.

    ref: b5-1066

  • sushant_ci
    sushant_ci
    Community Member

    Any update on this?

    With the workaround... does that work if I am the creator of my team? Rather not try it and risk losing data!

  • Jacob
    Jacob

    @sushant_ci We don't have any updates to share at the moment, but please keep an eye on the announcements at the top of this forum for some news. :)

  • roustem
    roustem

    @sushant_ci We deployed a new build last night. Please let us know if the workaround helped.

    Thank you!

  • sushant_ci
    sushant_ci
    Community Member

    @roustem that seems to have fixed it. Thanks!

  • Jacob
    Jacob

    @sushant_ci On behalf of Roustem and the team, you're welcome. :)

This discussion has been closed.