Google Inc.

Yahoo! Inc.

Naveen Agarwal

Guibin Kong

Eric Sachs

Brian Eaton

Mengcheng Duan

Lawrence Gordon Tesler

Jonathan Philip Levine

Arturo Bejar

Michael D Pinkerton

John Andrew Geishecker, Iii

Lee Kimball Cline

Aanchal Gupta

Christopher Michael Blessing

Daniel Alexander Hendricks

A virtual session manager of an electronic device maintains a web session for a user across multiple electronic devices. The virtual session manager receives an authentication request from a first electronic device that is in a communication range of the device. The virtual session manager transmits the authentication request to an endpoint device with a grant token without providing the first electronic device with any access to the grant token. The virtual session manager will receive, from the endpoint device, a first access token in response to the first authentication request. The virtual session manager will transmit the first access token to the first electronic device so that the first electronic device can establish a virtual session with the first web resource.

Authenticated session management across multiple electronic devices using a virtual session manager

A system maintains a web session across multiple web resources and/or devices using a two-token model. A user agent transmits an authentication request to a login endpoint. The user agent have access to a grant token, and it will receive an access token in response to the authentication request. The grant token is relatively long-lived and the first access token is relatively short-lived. The user agent will use the access token to access the first web resource and establish a web session. When the access token expires or is about to expire, the user agent will transmit a re-authentication request with the grant token to a re-authentication endpoint. The user agent will then receive a second access token from the re-authentication endpoint. The user agent will then use the second access token to access the web resource and maintain the web session.

Two-token based authenticated session management

A virtual session manager of an electronic device maintains a web session for a user across multiple electronic devices. The virtual session manager will receive an authentication request from a first electronic device that is in a communication range of the virtual session manager's device. The virtual session manager will transmit the authentication request to an endpoint device, and it will either present a grant token to or receive a grant token from the endpoint. The virtual session manager will receive a first access token from the endpoint device. The virtual session manager will transmit the first access token to the first electronic device so that the first electronic device can establish a virtual session with the first web resource without having any access to the grant token.

A system and computer-implemented method including receiving a request from a service provider, at a central account manager, to provide a user account for a user logging into the first service provider, identifying one or more user accounts associated with the user at one or more user account providers maintained at the central account manager, selecting a first user account of the one or more user accounts and providing, using the one or more computing devices, the selected first user account to the first service provider in response to the request.

Central account manager

Systems, methods, and machine-readable media for selecting an authentication process are disclosed. A system is configured to determine whether a user account on a client device is to be authenticated. If the user account is to be authenticated, the system is configured to transmit a request for a path indicator to an authentication path server. The request includes a user account identifier corresponding to the user account. The authentication path server is configured to select the path indicator based on the user account identifier. The system is further configured to receive the path indicator from the authentication path server, select an authentication process based on the path indicator, and initiate the selected authentication process.

Authentication based on path indicator from a server

A system and method for enabling, on any website, a unified user login that supports login through multiple known identity providers and, if necessary, the website's legacy login are disclosed. In one example, the system comprises a login receiver module, an identity provider determination module, a legacy account module, a federated account module and a login module. The login receiver module receives a login request associated with a user identifier. The identity provider determination module determines whether the login request is associated with a known identity provider. The legacy account module performs legacy account creation and/or legacy login verification when the address is not associated with any known identity provider. Otherwise, the federated account module performs federated account creation and/or federated login verification. The login module logs the user into the account responsive to one or more of verification and account creation.

Unified user login

A system and computer-implemented method including receiving a request from a first service provider, at a central account manager, to provide a user account for a user logging into a first service provider, identifying one or more user accounts at one or more service providers other than the first service provider associated with the user maintained at the central account manager, providing the one or more user accounts for display to the user, receiving a selection of a first user account of the one or more user accounts and providing the selected first user account to the first service provider in response to the request.

A network device and method are directed towards providing a client side sign-in seal for use detecting phishing attempts. In one embodiment, a user of a client device may provide anti-phishing data through a sign-in setup user interface for a website, application, or the like. In one embodiment, the anti-phishing data is an image provided by the user. The user may also provide text, symbols, an audio clip, or the like. The user may also modify aspects of the image, text, symbols, or the like, such as a color. When the user accesses the website, application, or the like, the client device may provide client device data used to locate and display the sign-in seal. If the user is being phished, the anti-phishing data may not be displayed or otherwise played.

Growing community of inventors

Fremont, CA, United States of America

Naveen Agarwal