In-Webo Technologies provides a Strong Authentication as a Service solution
The idea behind this module is to provide a strong and multifactor authentication method for Drupal sites, based on the validation of One-Time Passwords on our highly secured servers.
The solution is made of 3 parts
- The In-Webo servers hosting the InWebo SaaS authentication platform where administrators configure their websites to secure and create the users of these websites (users on InWebo are mapped on Drupal users, might be new users that will automatically added to the Drupal site at first successful authentication - self provisioning)
- The InWebo application installed on user desktops. It proposes browser extensions and acts as an OTP generator. Listing the secured sites as bookmarks, the extension submits the credential in the login form of the selected secured site
- The Drupal module that retrieves the posted credentials and sends them to our servers via a web service call and processes the answer (authenticates the user or not)
Communication between the Drupal site and our servers require a PEM (.crt) certificate that is generated on the InWebo platform.
The module administration panel allows to switch between Drupal standard or InWebo authentication methods.
User "admin" remains based on Drupal standard authentication.
Sandbox: http://drupal.org/sandbox/Emmanuel_N/1577980
Project page & doc : http://developer.inwebo.com/en/node/12
Drupal target version: 7.x
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | drupalcs-result.txt | 20.82 KB | targoo |
Comments
Comment #1
Emmanuel_N commentedComment #2
targoo commentedHi
There are still files other than README.txt in the master branch, make sure to remove them. See also step 5 in http://drupal.org/node/1127732
Review of the 7.x-1.x branch:
This automated report was generated with PAReview.sh, your friendly project application review script. You can also use the online version to check your project. Get a review bonus and we will come back to your application sooner.
Comment #3
targoo commented1) Could you rename readme.txt by README.TXT (Do you need the \r ?)
2) In your .info you can remove the 'files[] = ' (as well as the version)
For info only list files in the info file that contain classes or interfaces
3) Do you need an empty index.html file ?
4) inwebo.module
include_once() and require_once() are statements, not functions.
check http://drupal.org/coding-standards#includes
5) inwebo.module
"'access arguments' => array('administer inwebo'),": where does that permission come from?
6) inwebo.module
BAD : Implementation of hook_init().
GOOD : Implements hook_init(). Same issue elsewhere ;-)
We do really need more hands in the application queue and highly recommend to get a review bonus so we will(/can) come back to your application sooner ;-)
Cheers,
Comment #4
Emmanuel_N commentedHi,
I made a number of corrections according to your remarks and the results provided by the Drupal Code Sniffer. Most issues are solved and recommendations followed, yet some may persist.
About point 5), i changed 'access arguments' => array('administer inwebo'),
by a more generic access callback: 'access arguments' => array('access administration pages'),
Does it make sense?
Thanks a lot for your time
I'll try to participate and contribute to the review of applications in queue asap!
Cheers
Comment #5
Emmanuel_N commentedComment #6
FranciscoLuz commentedHi,
I did a manual review of your code. Here are some notes:
Comment #7
klausiClosing due to lack of activity. Feel free to reopen if you are still working on this application.
Comment #7.0
klausiAdded sandbox link, project page and drupal core targeted version