Client Data

In order to detect client types, Access Manager needs to recognize their identifying characteristics. These characteristics identify the features of all supported types and are defined in the amClientData.xml service file. The full scope of client data available is defined as a schema in amClientData.xml . The configured Access Manager client data available for HTML-based browsers is defined as sub-configurations of the overall schema: genericHTML and its parent HTML.

Parent profiles (or styles, as they are referred to in the Access Manager console) are defined with properties that are common to its configured child devices. This allows for the dynamic inheritance of the parent properties to the child devices making the device profiles easier to mange.

HTML

HTML is a base style containing properties common to HTML-based browsers. It might have several branches including web-based HTML (or genericHTML), cHTML (Compact HTML) and others. All configured devices for this style could inherit these properties which include:

parentId

Identifies the base profile. The default value is HTML.

clientType

Arbitrary string which uniquely identifies the client. The default value is HTML.

filePath

Used to locate the client type files (templates and JSP files). The default value is html.

contentType

Defines the content type of the HTTP request. The default value is text/html.

genericHTML—defines

Client that will be treated as HTML. The default value is true. This attribute does not refer to the similarly named generic HTML style.

cookieSupport

Defines whether cookies are supported by the client browser. The default value is true which sets a cookie in the response header. The other two values could be False which sets the cookie in the URL and Null which allows for dynamic cookie detection. In the first request, the cookie is set in both the response header and the URL; the actual mode is then detected and set from the subsequent request.

Although the Client Detection Service supports a cookieless mode, Access Manager console does not. Therefore, enabling this function will not allow login to the console. This feature is provided for wireless applications and others that will support it.

CcppAccept-Charset

Defines the character encoding used by Access Manager to send a response to the browser. The default value is UTF-8.

genericHTML

genericHTMLrefers to an HTML browser such as Netscape Navigator^TM, Microsoft^TM Internet Explorer, or Mozilla^TM. As a configured device, inherits properties from the HTML style as well as defining its own properties. genericHTML properties include the following:

parentId

Identifies the base profile for the configured device. The default value is HTML.

clientType

An arbitrary string which uniquely identifies the client. The default value is genericHTML.

userAgent

Search filter used to compare/match the user agent defined in the HTTP header. The default value is Mozilla/4.0 .

CcppAccept-Charset

Defines the character encoding set supported by the browser.
The default values are :
UTF-8;ISO-8859-1;ISO-8859-2;
ISO-8859-3;ISO-8859-4;ISO-8859-5;
ISO-8859-6;ISO-8859-7;ISO-8859-8;
ISO-8859-9;ISO-8859-10;ISO-8859-14;
ISO-8859-15;Shift_JIS;EUC-JP;
ISO-2022-JP;GB18030;GB2312;BIG5;
EUC-KR;ISO-2022-KR;TIS-620;KOI8-R

The character set can be configured for any given locale by adding charset_locale=codeset where the code set name is based on the Internet Assigned Numbers Authority (IANA) standard.