User's Manual

45
on an option string as third parameter. The Random Session String is stored in the session variable
Session("SessionString") for being used in the client response check.
3.
Request of the WebIdentity Client ActiveX object; the OBJECT tag enables inserting in the HTML document
the ActiveX univocally identified by means of the class id, which for the client ActiveX is 878A0D61-
48D2-11D3-A75D-00A0245382DE. The ID attribute identifies the object univocally inside the document
by means of a label thus enabling interaction. The CODEBASE attribute is necessary in case ActiveX is not
present on the client. Such an attribute specifies the location (URL) from which the ActiveX is downloaded
automatically. In addition to the URL it is possible to enter the control version ( #version= ) so that it can
be downloaded, if more recent than the installed version. The EMBED tag enables inserting in the HTML
document the client WebIdentity Plug-In univocally identified with the TYPE application/x-wicli-
plugin tag.
4. SendPIN function used during the submit phase for reading the User-Id from the token and for sending the
response to the web server.
5. Initialization of the WebIdentity client object with the Random Session String generated and sent by the
server; the entry RndSessionString is a variable of the client ActiveX inside the HTML document; the
Session("SessionString") entry is interpreted by the sever side and then replaced with a Random
Session String.
6. Initialization of the WebIdentity client object with the Label for token identification; the Label entry is a client
ActiveX variable inside the HTML document; the entry Aplication("wi_Label") is interpreted by the
server side and then replaced with the label chosen for the service.
7. Call of ReadPin method by the client ActiveX inside the HTML document for reading the encrypted User-Id
form the WebIdentity token; the value of the User-Id is assigned to the PIN variable contained in the
WebIdData Form inside the HTML document. The ReadPin is the function that generates the response to send
to the server.
8. Explicit call to the submit of the WebIdData form for actual sending to the web server via a POST of the PIN
variable containing the response.
9. Button inside the HTML document for authentication request by the user after inserting the WebIdentity token.
10. Variable hidden inside the HTML document used for storing the encrypted User-Id to send to the web server.