User specific
internet service provider (ISP) account information is stored on the user's
smart card, but the ISP specific connection information is stored within a
network computer client device (NC). When the NC is first powered on and used, it calls the relationship
server to receive connection information corresponding to the ISP that is either specified on the first user's
smart card or is otherwise chosen by the first user. This connection information is preferably stored in non-
volatile memory within the NC, so that even if the NC is powered down, it maintains the ability to connect to the ISP designated by its previous user. Each ISP is designated by a unique enterprise identification number assigned by the relationship
server. When a subsequent user inserts his
smart card into an NC, the NC compares the enterprise identification number on the smart card to the enterprise identification number within the NC. If the enterprise identification numbers match, the NC connects to the IAP already stored in the NC without dialing the relationship
server. Only if the enterprise identification numbers do not match must the NC then dial the relationship server to download connection information for the ISP designated by the smart card enterprise identification number. In the preferred embodiment, the ISP contents of the smart card are digitally signed by the ISP. If the enterprise identification numbers match, then the ISP contents of the smart card are cryptographically authenticated using the public key within the authorized usage
certificate for the ISP. If the cryptographic
authentication fails, then the NC reprograms the smart card.