weblogin

We need an IIS install to test the ISAPI filter. We should make sure to use compatible versions.

[phpwiki]
Included on this page:

* Objectives
* Prerequisites
* Download and Unzip Win32 Distribution
* Verify SSL Private Key Size (1024 bits required)
* Export SSL Cert and Private Key
* Setup Supporting Files and Registry Settings
* Request Encryption Key (Using Keyclient.exe)
* Add PubcookieFilter.dll to Your Website
* Test Pubcookie (with sample WebApp)

__Objectives__

Configured a more structured book arangement of the weblogin faq and added an install section. Also added some notes about the customization of the mod_pubcookie docs. I

t's a little hard to know how far to go with this. We could get pretty helpful if we prebuilt some modules for specific platforms. Obviously this could be extended over time.

Here's a thought, the deploy site could let folks login and then become contributors having the ability to upload builds for specific platofrms and even contrib notes.

The [install instructions for mod_pubcookie|http://www.pubcookie.org/docs/install-mod_pubcookie-3.0.html] need to be customized but only slightly. This is because the Apache user is likely to have to set up this configuration mostly on their own. There is simply less predictable work that we can do on the Unix platform, unless certain platforms are selected.

The areas that need customization in the base documentation are:
* where to find the granting certificate
* configuring the pubcookie config file (keymgt_uri)
* in general, example.edu can be replaced with uab.edu
* httpd.conf setting for Pubcookie module

The mod_pubcookie module requires Apache 1.3.x. In other words, pubcookie doesn't work with Apache 2.x.

It's possible that when a user bookmarks an application that uses weblogin, that they will wind up bookmarking the weblogin page and not the application page. This is because the first time the user goes to the application, they will likely be redirected automatically to the weblogin page to log in. When they see the user/passwd prompt, they will likely save the bookmark. Unfortunately this will record only the weblogin url and not the actual application they are trying to use.

It's important that a user wait until they have successfully logged in to their web application before setting their bookmark. This will ensure they are setting a bookmark for the correct web server.

We need to set up drupal on the demo site. Drupal is not going to look like does on our lab site. The motivation for drupal will be to help manage the content on the demo site. Think in terms of a webpage interface for devices like a wifi router.

The planned url scheme will be as follows:

* http://weblogin.ac.uab.edu
** main site with documentation for uab usage, demonstration, testing, config, and performance features
*https://weblogin.ac.uab.edu/login
** the link for initiating a web login
* https://weblogin.ac.uab.edu/logout
** the link for logging out