Mcafee, Inc.

Christopher M Roy

Shuborno Biswas

Junmin Qiu

Keefer T Davies

Dipeka Aj

Balaji Rao

Annapoorani Natarajan

Mechanisms for sharing user-provided information from an original equipment manufacturer (OEM) application and a vendor application are provided, the mechanisms including: receiving the user-provided information at the OEM application; determining a system identifier of a system on which the OEM application is executing at the OEM application using a hardware processor; providing the user-provided information and the system identifier to a vendor cloud server from the OEM application; determining the system identifier at vendor application; providing the system identifier from the vendor application to the vendor cloud server; receiving the user-provided information at the vendor application from the vendor cloud server in response to providing the system identifier to the vendor cloud server; and using the user-provided information to configure the vendor application.

Systems, methods, and media for sharing information with vendor applications in secure environments

A computer system, comprising one or more processors and a memory including instructions that, when executed, cause the one or more processors to at least: execute a first executable application; access a first registration request from a second executable application; validate a digital certification of the one or more components of the second executable; in response to the validating of the digital certification of the one or more components, save information from the first registration request into a registration store, wherein the information saved from the first registration request includes a unique identifier including (1) an identification of one or more types of events, and (2) a package family name; and send a raised event without requiring further authentication from the second executable application.

Authenticated discoverability of Universal Windows Applications to Win32 desktop applications

An example method includes executing a first executable application designed for execution using a first application programming interface (API). A first registration request is accessed from a second executable application designed for execution using a second API different from the first API, the first API and the second API executed within a same operating system environment. In response to validating of a digital certification of the second application, information from the first registration request is saved into a registration store. An event is raised having an event type and event information, and in response to determining that an event type of the raised event is saved in the registration store, the raised event is sent without requiring further authentication from the second executable application.

Growing community of inventors

Waterloo, Canada

Christopher M Roy