HTTP request parameters

When Z and I Emulator for Web makes a request of the CMS, it applies the appropriate HTTP parameters to this request. This helps determine the needs of the request. Since it must be an HTTP request, the CMS request interface is built around a standard HTTP-style query. Following the HTTPS protocol and server address is the query character, a question mark, and then a list of keys and values. These keys and values are separated by the ampersand symbol. Within each key and value pair, the key and value are separated by the symbol for equality. A sample query may look like the following example:

https://www.hcl.com/authserver/servlet/cms?operation=1
		&destination=www.hcl.com/somehost&appid=tpf
		&authtype=AuthType_3270Host

Table 5 is a list of available keys:

Table 1. Available keys and values
Key	Possible value
`operation`	'1' — Credential Mapping Request
`destination`	This is the destination for which the credentials are being requested.
`appid`	This is the host application ID for which the credentials are being requested.
`authtype`	This is the type of authentication credentials being requested (available authentication types are defined in Table 1).
`localid`	This optional value will supply the user's identification, based on the local operating system or the Portal user ID. For now, the local ID solution is supported only on the Windows operating system.