Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Simplify the Config UX to better explain HOTP vs TOTP #7

Open
aweingarten opened this issue Jul 5, 2016 · 2 comments
Open

Simplify the Config UX to better explain HOTP vs TOTP #7

aweingarten opened this issue Jul 5, 2016 · 2 comments

Comments

@aweingarten
Copy link

As a developer I would like the config screen here admin/config/people/tfa to do a better job explaining the difference between HOTP(one time code) vs TOTP(time based codes). I had to do a LOT of searching to understand what they were before I realized that the default most people want is TOTP

@therealssj
Copy link
Contributor

Yes, this is true. I see that in Drupal modules have these help pages where information related to the module is provided, what do you feel is better, information on the help page or directly on admin config page at admin/config/people/tfa

Maybe @nerdstein can provide some input as well.

@nerdstein
Copy link
Contributor

i think we should do a little of everything.

First, when your selecting, TOTP should probably be the first and default option.

Second, the selection should probably be "Time based code (TOTP)" and "One time code (HOTP)".

Third, I think a little bit of documentation on the form, as help pages, and in the readme.

My ten cents...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants