Microsoft Technology Licensing, LLC

George Li

Aravind Aluri

Joel Botner

Cherie Kwan

Dale Lemieux

Arik Cohen

Sarah Waskom

Huiyong Xiao

Tanmoy Dutta

David Benson Cross

Brian Scott Lounsberry

Sunil P Gottumukkala

Sunil Kadam

Ariye M Cohen

Sanjeev Dwivedi

Satyajit Nath

Felix Kasza

Marcelo J Birnbach

Daniel Carver

An applications programming interface (API) or other interface may be configured for use with a plurality of e-commerce applications and/or a plurality of payment systems. The API may be associated with an operating system of a client or may be otherwise located in an e-commerce system or network. The API may receive a call regarding a purchase transaction. The purchase transaction may be examined to determine if a payment method is synchronous or asynchronous. An appropriate payment system may be activated to perform the purchase transaction based at least in part on the determination made by the examination of the purchase transaction. A result of the purchase transaction may be sent to the e-commerce program. By revision of the API, developers of e-commerce applications are freed from the burden of revising code in response to the need to utilize additional or differently operated payment systems.

Extensible interface for synchronous and asynchronous payment

One or more techniques and/or systems are disclosed for generating a developer license that allows a developer application to run on developer machine. A user identification (userID) used to register a user can be used by the user to register as a developer. The userID can be authenticated for the registered developer. Further, a machine used by the developer for the developer application can be registered, and a resulting hardware identification (hardwareID) can be authenticated for the registered developer machine. Additionally, a developer certificate can be generated for the registered developer. The developer certificate can be authenticated and used to sign the developer application. The developer license can be generated for the developer, allowing the developer machine to execute the developer application, based at least upon the authenticated userID, the authenticated hardwareID, and the authenticated developer certificate.

Generating developer license to execute developer application

Global object access auditing techniques are described. In an implementation, a global SACL for a resource and an object SACL are merged to form a merged SACL responsive to a request for access to an object. The merged SACL is checked to determine what activity is to generate an audit event.

Global object access auditing

One or more labels are associated with a data object. One or more policies are associated with each of the labels. Based on the labels associated with the data objects, the associated policies are dispatched to policy decision engines to take one or more actions to enforce the policy. The labels, and the policies associated with the labels, are chosen by a business administrator within an enterprise, and are implemented by an Information Technology (IT) administrator. The association between labels and polices allows the policy to be applied to an object to be decoupled from the characterization of the nature of the object, or its purpose and/or role within an enterprise, business purpose and/or context of the object. Examples of policies are: access, backup, retention, isolation, audit, etc.

Labeling of data objects to apply and enforce policies

Growing community of inventors

Redmond, WA, United States of America

George Li