Abstract: A distributed computer system and server architecture transmitting an electronic ticket over the system, such as the Internet, enabling a user to be authenticated and authorized for a requested operation. An “eticket” architecture (including identification information) is generated by, for example, an authentication server. The information in the eticket is hashed using, for example, a Message Digest Protocol, and a hash number is generated. The hash number is then encrypted by the authentication server using a private key, and the identification information in the eticket and the encrypted hash number are concatenated by the authentication server to generate a completed “eticket” architecture. The “eticket” may then be transmitted over the Internet (i.e., a non-secure environment) from server to server without having the information in the “eticket” altered, and without having to “reauthenticate” the user at each server.

Abstract: A computer program memory stores computer instructions for securing data transmitted over a system, such as the Internet, enabling a user to be authenticated and authorized for a requested operation. An “eticket” architecture (including identification information) is generated by an authentication server. The information in the eticket is hashed using, for example, a Message Digest Protocol, and a hash number is generated. The hash number is then encrypted using a private key, and the identification information in the eticket and the encrypted hash number are concatenated to generate a completed “eticket” architecture. The “eticket” may then be transmitted over the Internet (i.e., a non-secure environment) from server to server without having the information in the “eticket” altered, and without having to “reauthenticate” the user at each server.