The Swekey USB Token is a low cost USB device with a unique signing.
It contains a 32 bit unique hashcode and some software for generating
authentication code sequences based on a random token and the hashcode
on the USB Token itself.
This module integrates the Swekey Token into the Drupal user module, adding
a third level of protection on top of the username and password.
Why should I use it?
If your website or webapplication needs extra protection, or your users
think they need it ;-)
Why not use the original module from Musbe, the creators of the Swekey?
Several reasons. The original module does not integrate well with the session
handler. It assumes we are all using the file method, storing the session data
on disk. Problems also arise for clusterd fileservers because of this.
Second. The Swekey system uses external authentication servers. That's ok, but
one of them is used for generating a random token. Drupal really doesn't need
that because we have a unique token already by way of the unique form-id.
Than finally, for checking purpuses the hashcode from the Token is send to
the authentication server. Unencrypted. The servers from musbe are simple
http servers.
Why use this module?
It is not dependent on any external server. It leverages the full Druapl API.
This is a companion piece to the Google Analytics module.
Google Analytics is a free service that tracks users, demographic, and statistical data. On a typical site it is easy to set up --especially in Drupal using the Google Analytics module. Under a typical set-up Google Analytics tracks a user as he/she navigates from page to page within a site. This is fine for a typical site where every action on a site requires a new page view. What if, however, the site owner wanted to track how a user is using the ajax form built into views or some other custom ajax event. Google Analytics has a control for this called Event Tracking.
Event Tracking is a way to track user interaction with out registering a page view. Using Google Maps as an example site, event tracking would allow the user to track Zoom, Drag, and View Change events without contaminating the page view statistic.
This is an API module; it just provides a new form element type for use in
other modules. Just set '#type' => 'smileyslider' and optionally set the #range to a positive integer (it defaults to 10) and the value of the
element when submitted will be an integer between 0 and the #range,
indicating the user's happiness. For example:
$form['smiley'] = array(
'#type' => 'smileyslider', // required
'#range' => 100, // defaults to 10
'#title' => t('Happiness'), // only shows for users with JS disabled
'#required' => TRUE,
'#default_value' => rand(0, 100), // random amount of happiness
);
Because it only provides a new form element type, this module has no effect on
your site by itself. Another module has to use the form element type.