Symantec Corporation

Early Warning Services, LLC

Payfone, Inc.

Prove Identity, Inc.

Alan Dundas

Gregory Slowiak

Andrew Robert Rolfe

Eirik Herskedal

Nicolas Popp

Mingliang Pei

Siddharth Bajaj

Liyu Yi

Oanh Hoang

John Smith

Thomas Harning

Aaron Diers

Provided is a method for authenticating a user communicating with an enterprise via a network. The method includes receiving, via the network, authenticators for a user from a first user device associated with the user, and storing the received authenticators. A first authenticator from the stored authenticators is selected to be used for authenticating the user based on an authentication policy received from the enterprise. An authentication request is transmitted to a user device requesting the first authenticator and the user is authentication by comparing the received authenticator with the stored first authenticator.

Authenticator centralization and protection including selection of authenticator type based on authentication policy

User authentication based on device identifier further identifying software agent

Authenticator centralization and protection based on authenticator type and authentication policy

Provided is a method for authenticating a user communicating with an enterprise via a network. The method includes receiving, via the network, authenticators for a user from a first user device associated with the user, and storing the received authenticators. A first authenticator from the stored authenticators is selected to be used for authenticating the user based on an authentication policy received from the enterprise. An authentication request is transmitted to a user device requesting the first authenticator and the user is authentication by by comparing the received authenticator with the stored first authenticator.

Authenticator centralization and protection

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.

Method and system for smartcard emulation

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.

Authentication of PKI credential by use of a one time password and pin

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.

Service assisted reliable transaction signing

A computing system of an authentication service provider receives a federated identity protocol request triggered by a relying party to validate a user. The federated identity protocol request includes a user identifier of an authenticated identity. The computing system searches mapping data stored in a data store that is coupled to the computing system to identify a type of virtual token associated with the user identifier and authenticates the user by requesting the identified type of virtual token from a user device and verifying a virtual token received from the user device using the mapping data. The computing system sends second-factor authentication results to the relying party via the federated identity protocol.

Strong authentication via a federated identity protocol

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.

Growing community of inventors

Los Altos Hills, CA, United States of America

Alan Dundas