Hi - I'm working on a library system and adding a "kiosk mode" (possibly using the <a href="http://drupal.org/project/kiosk">Kiosk module</a>)<br><br><ol><li>The site essentially presents the same information whether a user is logged in or anonymous.</li>
<li>The Drupal site uses a custom authentication plugin; authentication is actually done on the remote backend library server<br></li><li>A regular user logged in over the internet to a normal Drupal account can do things like request books, check account, etc, using Drupal the way it normally works.<br>
</li><li>A kiosk user (probably anon user) can do things that require authentication, but it must be a one-time authentication to the back-end server. We're calling it "transactional authentication". Basically, they'll never do a Drupal login, but when they want to do something that requires authentication, they'll provide their library number and password for one specific transaction (like requesting a book).</li>
</ol>I'd sure appreciate your suggestions about how best to do the "transactional authentication" part. It's pretty easy to start hacking at, but perhaps someone can suggest an elegant approach to this.<br>
<br>Thanks,<br>-Randy<br><br>-- <br>Randy Fay<br>Drupal Development, troubleshooting, and debugging<br><a href="mailto:randy@randyfay.com">randy@randyfay.com</a><br>+1 970.462.7450<br><br>