TOTP?

zendnez

The latest beta notes include:

[NEW] TOTP fields editing and view.

Is this intended to mean that TOTP's are being computed and displayed? They aren't working for me - I just see an empty field.

Thanks.

---

1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Sync Type: Not Provided

SergeyTheAgile

@zendnez TOTP should be computed, displayed and copied. If it's not working - there might be 2 reasons - bug in the app or malformed data.

Do you see TOTP field when you click Edit button? If yes, do you see your secret (DON'T PUT IT HERE! :) ) with characters abcdefghijklmnopqrstuvwxyz234567 or there are other characters as well?

If there is no TOTP field, type /raw in the search box to see raw item data, do you see TOTP anywhere in "Details JSON" tab?

Please feel free to drop a line at support+windowsbeta@agilebits.com for more assistance, but do not send us your secrets! ;)

zendnez

@SergeyTheAgile What I see is a field labeled OTP with no value displayed.

When I look at the raw data for the TOTP field, I see the following field:

 "fields": [
    {
      "k": "concealed",
      "n": "TOTP_{obfuscated}",
      "v": "xxxx xxxx xxxx xxxx xxxx xxxx xxxx xxxx",
      "t": "OTP"
    }
  ],

I replaced a portion of n with {obfuscated} and replaced the TOTP seed with x's. The TOTP value is valid for sure. I have a number of accounts all with valid/working TOTPs and they are all displaying this way.

Is it possible that you're not handling the spaces in the TOTP value?

zendnez

@SergeyTheAgile Following up to my own post. I was right...you're not handling the spaces. This entry was in a local vault. I copied it up to a Teams-based vault so I could edit it. I removed the spaces, and it worked.

For what it's worth, 1Password4 for Windows as well as your Mac, iPhone, Android versions all handle spaces. So do the Authenticator apps on major platforms. Easy fix for you. :)

SergeyTheAgile

You are totally right, spaces are not allowed today... Yet ;)