Since the server requesting this information is on a secure web server, this information is encrypted before being sent from the clients web browser to server. The server uses the principal name and password to verify that the user is who they say they are. If this verification succeeds, the server then informs the user's web browser to set a cookie which will be transmitted to all web servers in the ucdavis.edu name space. Finally, having set the cookie, the web server passes the client back to the web page which was initially requested by the user for access. Upon returning, when the client's cookie is checked and found to be authentic, access to the requested document is granted.
User launches an SSL-capable browser.
User attempts to open a document that is secure on a local UCD server. If user is authenticated, the document is processed. If all is ok, the document is presented. If the user's cookie is valid, the page is presented. If even higher level of access control is required, server can check against local access database before presenting the page If the cookie is not valid or not in existence, the local web server will contact the SecureWeb server for assistance in establishing authentication.