Identity Management Services

1. Prerequisites

• Supported SSL Capable (HTTPS) Server:

  • Netscape Enterprise/FastTrack 2 or 3

  • Apache-based (Stronghold, Raven, mod_ssl)

• VeriSign or Thawte certificate for the server

• Perl Version 5.8.0 or greater

If your application runs on www.ku.edu, www2.ku.edu, or apps.ku.edu then you already meet the above conditions.

2. Get and install the application libraries

If your application runs on www.ku.edu, www2.ku.edu, or apps.ku.edu the application libraries are already installed on your system.

Otherwise, you may download the application library source at
     http://www.aims.cc.ku.edu/argus-client/KuPortal-3.3.4.tar.gz

If you need to install the libraries, you may also need to install the lib-www package of Perl modules, along with the Crypt::SSLeay module. This is beyond the scope of this document at this time. Contact Identity Management Services if you need assistance.

You will also need to install the KUssl library at
     http://www.aims.ku.edu/argus-client/KUssl-1.00.tar.gz

3. Contact Identity Management Services and discuss your application

You will need to contact Identity Management Services at aims@ku.edu to decide what information you need to authorize users for your application. You may need permission from Human Resources or the University Registrar to receive this data. Identity Management Services will figure out what you need to do to get going.

You will need a local Argus SSL certificate generated to identify your application to the backend login server cgi. Identity Management Services will generate this for you and help you get it installed for your application.

They will also authorize your application to use the Argus login server.

4. Test the Installation

Download the test CGI program test-argus.cgi and temporarily put it in place of your application CGI.

Open the URL for your application. On accessing the URL, you will see a page indicating that you are not logged in and offering a login button. Upon clicking the login button, you will be directed to the Argus Login page. Upon logging in, you will be directed back to the test-argus.cgi script, which will display your user information.

1. Pre-login (your server)

2. Argus Login (access.aims.ku.edu) - prompts for Online ID and password.

3. Post-login (access.aims.ku.edu) - authenticates your ID and password.

4. test-argus.cgi display (your server)

If test-argus.cgi does not work correctly, there is probably a problem of some sort with the Argus authorization. Email a description of the problem and any error messages to argus@ku.edu.

5. Create your application

Replace the test-argus.cgi code with your actual application CGI, which will use the Argus libraries to identify your users.

6. Arrange for Periodic Cleanup of Your Application's Login API Cache

In normal operation, each user logging in to your server with Argus will record data in a Berkeley DB file in your
    $HOME/.argus/loginapicache
directory.

You should contact argus@ku.edu for information on keeping these files clean.