iTP Secure WebServer System Administrator's Guide (iTPWebSvr 6.0+)

Configuration Directives
iTP Secure WebServer System Administrator’s Guide—523346-002
A-55
Anonymous Ticket Attributes
Cookies that have a persistence greater than 0 can be stored in the web client,
across browser sessions so that sessions can continue across browser restarts,
whether or not the session is anonymous.
This attribute is effective only for anonymous ticketing (see Anonymous Ticketing
on page 11-1). For non-anonymous tickets, the ticketing agent controls how long
the ticket is valid.
The following default applies:
-CookiePersistence 0
To use -CookiePersistence in an SI_Default Region command, enter the
following:
SI_Default -CookiePersistence 1800
-EnableAnonymousTicketing {GroupID GroupID ...}
The EnableAnonymousTicketing attribute turns on anonymous ticketing for
regions accessible to the specified groups. Anonymous ticketing enables you to
track requests without performing authentication or authorization. For more
information about anonymous ticketing, refer to Anonymous Ticketing on
page 11-1.
The department ID in a directive or command that enables anonymous ticketing
can be any string, as long as it does not include spaces.
If you include only one group, you may omit the braces.
Omitting the group IDs turns off anonymous ticketing for all regions in the specified
department.
The default is no anonymous ticketing.
To use -EnableAnonymousTicketing in an SI_Department Region
command, enter the following:
SI_Department Mydepartment -EnableAnonymousTicketing { 10 20
30 }
-PostExpirationExtension add-seconds
For requests using a POST method, the PostExpirationExtension attribute
adds a specified number of seconds (add-seconds) to the normal lifespan of the
Session Identifier.
The PostExpirationExtension directive allows clients sufficient time to GET a
form, fill it out, and POST it back to the iTP Secure WebServer. Without the
additional time specified by the PostExpirationExtension directive, the
session identifier might expire before the web client POSTs the form and cause the
content server to redirect the POST message to the ticketing agent for
reauthentication; as a result, the data from the POST message would be lost.