Enpass currently works well with the standard TOTP implementation of a numeric, 30 second interval TOTP code which makes it possible to use most services that offer this sort of authentication. Due to it supporting custom digits, it not only works with the standard 6-digit, but also with some different ones like Blizzard's 8-digit authenticator (which I use just fine with Enpass).

What Enpass still lacks in this regard is support for custom time interval and also Steam's 5-digit alphanumeric standard.

I, for instance, have to use another authenticator for services like 'Twitch' and 'Mercado Livre' which use 7-digit 10-second TOTP codes (which I believe is Authy's own standard) and Steam (I believe Bitwarden is the only one that currently offers working TOTP for all of these).

 

I know there's currently a thread which is a little over 4 months old about Steam's TOTP, but I couldn't find anything regarding custom time intervals in the feature request so I figured I should post it and hope it gets done sometime in the future

still a valuable feature but at least twitch back pedaled and allows for standard totp now, so that's great

Upvote for this feature.

Also, cross link to same request at https://discussion.enpass.io/index.php?/topic/17068-support-for-period-parameter-for-totp/

2022 has come...

Hi @romkazor

Our dedicated development team is working on implementing the requested feature on a priority. I will not be able to share any ETA for the same but rest assured, I have shared the comments as feedback with them. Enpass appreciates your support and patience in the meantime.

#SI-1254

Any news on this?

It’s already 2024, and this problem still hasn’t been resolved.

Just to document for anyone interested in knowing the custom TOTP parameters supported today (09/2024) by Enpass:

• otpauth:

• algorithm = SHA1 / SHA256 / SHA512
• digits = 6–8
• period = 2–60

Not yet supported:

• steam