We need to test the per-application custom logout message feature that is part of the login server. We need to determine if this is a service we want to provide to application writers on campus.
Test Per-app logout page configuration
app_logout configuration
Submitted by pravenj on Mon, 03/15/2004 - 18:03.
#
» login to post comments


app_logout configuration
#custom logout messages in config file:
usage: app_logout_string-(app server name)-(application to serve):(html message)
app_logout_string-polka.it.uab.edu-webapp:
In this the app_logout_string can be associated to any app server of choice (here polka.it.uab.edu and the webapp). multiple variations of these can be written for multiple app servers. This changes line 2 of the message after logout for options 2 and 3 of logout process.
templates in the login_templates folder:
logout_weblogin: gives 3 line of message in the complete logout option (option 3 logout).
logout_time_remaining: gives 3 line in logout process 2. The remaining time is given through variable %remaining%
logout_already_weblogin: gives the message already logged out if you try to invoke the 3rd option again after logging out.
logout_app: this is the default message that is displayed if the app_logout_string is not set properly for an app server in the config file.
logout_app_custom: this is the template that is going to be displayed if you set the app_logout_string properly.
logout_part1: message to completely exit browser.
logout_part2: copyright info currently set to Acme
logout_postscript_still_others: Warning message with logout option 3.
logout_postscript_still_weblogin: Warning message with logout option 4.
logout_still_weblogin: line 3 of logout message from logout option 2.
All these files can be modified using html to suite needs.