Forum Discussion

DenalB's avatar
DenalB
Super Contributor
5 years ago

CMS software WoltLab Suite: TOTP field not detected

Actually, the "WoltLab Suite" is available in version 5.3. In this version, there is basically no possibility to enable 2FA. But there is an extension available which enables this feature, and it works like a charm with 1Password. The field for entering the TOTP is detected as it should be.

Here is a working example:

Now there is version 5.4 RC2 of the "WoltLab Suite" available for testing and here 2FA options are available. The problem is that the TOTP field is not detected anymore. So there is no possibility to autofill or manually fill the TOTP code. The only thing that works is drag and drop the code into the TOTP field.

Here's an example:

When comparing websites, you can see the differences between now and before.

Version 5.3 with extension installed:
<input type="text" name="twoStepCode" id="twoStepCode" autocomplete="one-time-code" required="" class="" data-com-onepassword-filled="light">

Version 5.4 RC2:
<input type="text" id="code" name="code" value="" class="multifactorTotpCode" inputmode="numeric" autocomplete="off" pattern="[0-9]*" autofocus="" required="" minlength="6" maxlength="6" placeholder="123456" size="6">

I asked the developer to change the naming of the field, but they don't want to change anything from their side.

Link to the developer of the CMS software:
https://www.woltlab.com

Link to the German discussion in the WoltLab-Community for that issue:
https://community.woltlab.com/thread/290984-einmalcode-automatisch-ausf%C3%BCllen-passwort-manager/

If you register a new account on this website, you should be able to enable 2FA on https://www.woltlab.com/account-security/ and test this behavior. They already are using version 5.4 RC2.

I already collected website information with the help of the 1Password extension. I didn't have the possibility to save the collected information. I clicked the button and nothing happened... Did you get them?

The problem is that this issue will affect all websites which will be using the CMS software if it is available as a final release. Hopefully you can help here.

1Password Version: 1Password for Windows 8.1.2-2.BETA
Extension Version: 2.0.5.beta in Vivaldi
OS Version: Windows 10 21H1
Sync Type: 1Password.com

browser extension

18 Replies

Show More
  • DenalB's avatar
    DenalB
    Super Contributor
    5 years ago

    Next time, please feel free to add the page details directly in the forum discussion then, so we keep everything in one place
    Good to know! :+1:

  • Former Member's avatar
    Former Member
    5 years ago

    DenalB:

    Understood, I thought you wanted to keep the discussion private since you emailed us after opening the discussion on the forum :+1:

    Next time, please feel free to add the page details directly in the forum discussion then, so we keep everything in one place and we can reply in a single discussion without having to collect information from multiple places ;)

  • DenalB's avatar
    DenalB
    Super Contributor
    5 years ago

    Thanks, @ag_ana !

    and someone will get back to your email as soon as possible
    It would be okay to get back to me here, so that others also have the possibility to get this information. ;)

  • Former Member's avatar
    Former Member
    5 years ago

    DenalB:

    Thank you! I confirm that I have managed to locate your message in our system :+1: We will take a look and someone will get back to your email as soon as possible.

    Thank you for your patience!

    ref: AHV-16592-253

  • DenalB's avatar
    DenalB
    Super Contributor
    5 years ago

    Just send the collected website information to you via email.

    Here's the ticket ID I got back: #AHV-16592-253

  • DenalB's avatar
    DenalB
    Super Contributor
    5 years ago

    Hi @WoltLabTim !

    Thanks for jumping in. :+1:

  • Former Member's avatar
    Former Member
    5 years ago

    Hi

    DenalB Thank you for creating this topic.

    Let me please clarify one paragraph of the initial message:

    I asked the developer to change the naming of the field, but they don't want to change anything from their side.

    The discussion in the linked German thread within WoltLab Community revolved around the use of autocomplete="off" vs autocomplete="one-time-code".

    As it turned out setting autocomplete="one-time-code" causes stock web browsers (without a password manager extension) to store and suggest previously used TOTP codes which we consider to be bad user experience.

    We're happy to accommodate changes to the field (e.g. a different name attribute) if this would help 1Password detecting this field. However the use of autocomplete="one-time-code" appears to worsen the UX for the majority of users that don't use 1Password.