| Project: | Google Authenticator login |
| Version: | 7.x-1.x-dev |
| Component: | Documentation |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | fixed |
Issue Summary
Hi, this might be obvious to some.. but how exactly to you make this module work?
The Readme.txt file simply says:
Dependencies
------------
* QR Codes
* ga4php, you only need the libraryInstall
-------
Install as usual and copy the ga4php.php file to your module folder.
ok, so I found ga4php on Google's code site.
http://code.google.com/p/ga4php/
again, now what? there's no real documentation included with those files either.
do I just copy all these files over to my root drupal install or in this modules directory? (where exactly?)
Is there any code modifications I need to do before I enable this module?
I noticed some token values in the ga4php.php that comes bundled with this module. Do I use this file? or the one that's included with the Google Code download?
just need some guidance in making this work!
thanks
Comments
#1
You're right, the README is a bit outdated, you only have to download http://drupal.org/project/mobile_codes and enable both modules, that should be enough.
The library is included.
#2
thanks for the info! I got the other module installed and the library required.
I have both addons enabled.
Now what? I don't see anywhere to configure this module? Do I have to update any files manually?
Where do I register this with Google's Authentication service?
I'm sorry, I don't mean to be rude, but these are the types of instructions we need to configure and use your module! :)
thanks
#3
#2 You just have to set permissions, to control who can use it and who has to use it. You don't have to register anything, this works stand alone.
Once logged in you go to your account page (/user) and you'll see a new tab for the GA login, it's a small wizard that guides you through the process. At the end it will present you a QR code you can scan using the Google Authenticator App on your phone.
I'll ask my colleague to write some docs with screenshots tomorrow.
#4
ahh perfect! Now it all makes sense to me!
Thanks so much for your help and sorry for my "attitude"! :)
#5
#4 no need to apologize, docs are lacking ;-)
#6
Here's a first step at a reworked README.txt file that seems to answer the questions raised in this issue.
#7
Fixed