Closed (works as designed)
Project:
Two-factor Authentication (TFA)
Version:
8.x-1.x-dev
Component:
User interface
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
13 Feb 2017 at 17:38 UTC
Updated:
16 Jan 2018 at 19:09 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
therealssj commentedHave you installed Google Authenticator Login?
Comment #3
Techbot commentedNope, I 'm not using google authentication login.
From what I can see there are three validation plugins already in the folder, Hotp, totop and codeValidation or something similar.
These are not visible in the admin meaning they are incomplete.
I could install another plugin but that is not what this issue is about. The issue is why the default example plugins already in the package are not visible.
Do they need to be
a) removed
b) fixed
c) better documented.
Comment #4
gregglesYou shouldn't need to use Google Authenticator Login. This module provides a different way to achieve the same thing (TOTP) as GA Login. GA Login only supports TOTP and not fallback codes, sms, etc.
What did you do to revert to a clean install?
Comment #5
Techbot commentedrevert to clean install=
1) complete clean install using docksal.
2) Upgrade Drupal to latest version
3) change composer to "minimum-stability": "dev"
4) Install tfa (encrypt amd key)
5) Install Real AES. (because of previous bad dx issue)
6) Setup Key and Encryption profile
See image
There are three pluggins in the directory but none to be seen in admin, none have setup files.
Comment #6
sanduhrsSame issue here:
Fresh install on Linux, PHP 7.1.11
Any hints?
Comment #7
sanduhrsAdding Google Authenticator login to the Setup, I was able to make it work. Thanks
Comment #8
daggerhart commented@therealssj - Any reason not to move the TOTP and HOTP plugins to the ga_login module, since that is the only thing that can use them?
Also, when no validation plugins are available, the settings page should list links to some other contrib validation modules and help guide the user.
Comment #9
daggerhart commentedMarking as closed because the specific issue was resolved. We've also improved the README in recent releases to hopefully better guide users in setting up this module.
If there are more questions or concerns around this error message, please open a new issue.