• Resolved mountainguy2

    (@mountainguy2)


    Hi, am frustrated. Setting up cell phone sign in and already noticed some user unfriendly things.

    1. Please make dialog box in the test screen the same length as the activation code!

    2. Make activation codes easy to type, rediculous to have mixed case for this sort of thing, just give it all in lower case, preferably all alpha not numeric, or all numeric and not alpha. I mean, are we trying to make bank passwords here, or just a cell phone activation code!?

    3. Remove period at end of activation code shown on phone, it appears to be part of the code.

    MTN

    https://www.ads-software.com/plugins/wordfence/

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author WFMattR

    (@wfmattr)

    Hi,

    Thanks for the feedback — we do have some UI changes planned across the plugin, and will be sure to take a look at these items!

    -Matt R

    Thread Starter mountainguy2

    (@mountainguy2)

    Ok, thanks.

    Thread Starter mountainguy2

    (@mountainguy2)

    I’d add that an important feature Wordfence needs is that once a cell phone sign-in has been implemented, BUT NOT YET ACTIVATED, that user should be blocked from logging in. Basic security, as in if cell phone sign-in is being implemented, why is that, if the user can still login without 2-part? Having it set up the way it currently works is immature from a security standpoint.

    The above turns out to be what confused my last attempt to set this up. The user kept using their login and never sent me the code for the activation. They needed a nag message when they tried to login.

    MTN

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Cell Phone Sign In, feature request’ is closed to new replies.