Abstract: A method and system for emulating a smartcard which includes receiving a one time password and a container PIN for a container, validating the container PIN, upon validating the container PIN, and sending a request to validate the one time password to an authentication server based on a credential ID and a user ID, wherein the request includes the credential ID, the user ID, and the one time password. Upon validation of the one time password by the authentication server, a response is received from the authentication server, and the response includes at least one of: at least a portion of a private key or an authorization to access a at least a portion of the private key stored locally.

Abstract: A method and system for authenticating a credential via a one time password which includes receiving a user ID, a client ID, and the one time password from a client device, and then validating the one time password based on the user ID and the credential ID. Upon validating the one time password, a response is sent to the client device, and the response includes at least one of an authorization to access a private key stored on the client device or at least a portion of the private key.

Abstract: Techniques are disclosed for authenticating transactions conducted over computer networks, e.g., online banking transactions or other transactions performed by a financial institution at a customer's request. After receiving a transaction request (and associated transaction details), the transaction signing service signs the transaction data and sends the resulting blob to the user requesting the transaction. After being transmitted to the user, the signed transaction data itself is then signed using PKI credentials of the user, which then returns the twice-signed bundle to the financial institution. Rather than rely on the cryptographic signature of the client, the financial intuition (or other replying party) validates that the transaction data signed using its own highly trusted key has not been altered prior to being signed and returned by the client.

Abstract: A script hosting server receives a script from an authenticated source, associates the script with a certificate profile for digital certificates based on input from the authenticated source, receives user enrollment information for the certificate profile from the authenticated source, receives a script request of a client device, the script request identifying the certificate profile and a user of the client device, determines whether the user is enrolled in the certificate profile based on the user enrollment information, and, upon determining that the user is enrolled, providing the scripts to the client device.

Abstract: Techniques are disclosed for authenticating transactions conducted over computer networks, e.g., online banking transactions or other transactions performed by a financial institution at a customer's request. After receiving a transaction request (and associated transaction details), the transaction signing service signs the transaction data and sends the resulting blob to the user requesting the transaction. After being transmitted to the user, the signed transaction data itself is then signed using PKI credentials of the user, which then returns the twice-signed bundle to the financial institution.

Abstract: Techniques for identifying a smart card in a plug and play system. The technique requires identifying a unique code identifier and loading a smart card minidriver according to the unique code identifier.

Abstract: Described herein is a filter driver in a smartcardreader class that recognizes the presence of a smartcard in a smartcard reader and creates a device node (devnode).

Abstract: A filter driver may be instantiated in a smartcardreader class, and used to modify the smartcard status in an operating system.

Abstract: Techniques for identifying a smart card in a plug and play system. The technique requires identifying a unique code identifier and loading a smart card minidriver according to the unique code identifier.

Abstract: Described herein is a filter driver in a smartcardreader class that recognizes the presence of a smartcard in a smartcard reader and creates a device node (devnode).

Abstract: A filter driver may be instantiated in a smartcardreader class, and used to modify the smartcard status in an operating system.