Microsoft Technology Licensing, LLC

Auth0, Inc.

Okta, Inc.

Tomasz Janczuk

Giovanni Moises Della-Libera

Vijay Gajjala

Elliot Lee Waingold

Matías Woloski

Christopher G Kaler

Erik B Christensen

Kenneth David Wolf

Stephen James Millet

David Wortendyke

Stefan Harrington Pharies

Craig Andrew Critchley

Uday Sooryakant Hegde

Stephen T Swartz

Michael Steven Vernal

Shy Cohen

Douglas A Walter

John Robert Lambert

Vaithialingam Balayoghan

Yaniv Pessach

Nicholas Alexander Allen

Richard L Hasha

Melissa Wood Dunn

James Ernest Johnson

Tirunelveli R Vishwanath

Lance Olson

Richard Douglas Hill

Stefan R Batres

Umesh Madan

Michael James Coulson

John David Doty

Michael Marucheck

Krishnan Srinivasan

Matthew Thomas Tavis

Geary L Eppley

David Edwin Levin

Richard Dievendorff

Max A Feingold

Eric Kenneth Zinda

Douglas M Purdy

Natasha Harish Jethanandani

David Owen Driver

Aaron Stern

Saurab Nog

Siddhartha Puri

Anastasios Kasiolas

Jesus Ruiz-Scougall

Kapil Gupta

Vipul A Modi

Ryan Thomas Sturgell

Alexander Martin DeJarnatt

Mohammad Makarechian

Jonathan T Wheeler

Scott Christopher Seely

Sowmyanarayanan K Srinivasan

Evgeny Osovetsky

Michael Thomas Dice

Chaitanya Dutt Upadhyay

Mauro Ottaviani

Erin Honeycutt

Yasser Shohoud

Alfred M Lee, Iv

Eugene Shvets

Serge Sverdlov

Jonathan M Cole

Vaithialingam B Balayogan

Mohamed-Hany Essam Ramadan

Anand Rjagopalan

Yavor Georgiev

Matias Woloski

A multitenant infrastructure server (MTIS) is configured to provide an environment to execute a computer routine of an arbitrary application. The MTIS receives a request from a webtask server to execute the computer routine in a webtask container. The computer routine is executed in the webtask container at the MTIS. Upon successful execution of the computer routine, a result set is returned to the webtask server. If the execution of the computer routine is unsuccessful, an error notification is returned to the webtask server. The resources consumed during the execution of the computer routine are determined. The webtask container is destroyed to prevent persistent storage of the computer routine on the MTIS.

Multi-tenancy via code encapsulated in server requests

A signature system with a mechanism to identify element(s) of a signed document includes a sender having a signature module with a digest generator. The digest generator generates digests for identifying selected elements of the document. The resulting 'identifying' digests are then used in generating a signature in which the sender signs the digests rather than the original elements. The receiver can then process the signature and use these digests to distinguish between elements, as needed.

Digests to identify elements in a signature process

The present invention extends to methods, systems, and computer program products for routing requests for duplex applications. Embodiments of the invention provide a multi-machine scalability mechanism for duplex messages patterns based on a polling mechanism. Client requests and polls can be distributed to service instances running within a cluster of machines by a session-unaware load balancer. Messages to and from a given client can be accessed by any service instance in the cluster service instance, which allows capacity scale-out and seamless failover between service instances. A coordinated inbound message store is used to affinitize application requests to a particular service instance. A coordinated outbound message store is used to route application responses from the machine running the application to the machine where a polling request arrived. Further, the lifetime of the service instance is decoupled from the inbound or outbound message stores, allowing the client-server conversation to potentially span many instances of the service.

Routing requests for duplex applications

The present invention provides for an automated, user friendly way of constructing and using a binding object. A developer is presented with and selects binding elements that will ultimately be used to create a runtime communication channel for transporting a message between a client and service endpoint. After receiving the user input, metadata, a channel factory and listener factory are created. The metadata describes binding elements and provides an abstract representation of a protocol stack that implements communication aspects at runtime. The channel factory is configured to use the collection of metadata at runtime to generate the runtime communication channel. Further, the listener factory is configured to accept the runtime communication channel for de-multiplexing the communication aspects in order to process the message at a service endpoint. The present invention also provides for groupings of binding elements and standardized binding objects organized based on industry need.

System and method for building and using communication binding objects

A security system with a mechanism to identify types of information that need to be secured and another mechanism to specify how the types are to be secured. The system includes a sender having an application and a receiver having a security module and one or more datastores to store information related to types of information that need to be secured (e.g. 'scopes'), how information is to be secured (e.g., 'profiles'), and a mapping (e.g., &#x201c;bindings&#x201d;) between the scopes and profiles. Scopes can be implemented by application developers. Profiles can be implemented by application deployers and/or administrators. The security module determines which scope is appropriate for the message, and then determines the profile that is mapped to the scope. The security module can then make an access control decision using the profile.

Security scopes and profiles

A system for processing multiple types of security schemes includes a server having a claims engine that extracts claim(s) from security token(s) and maps extracted claims to other claims. The term claim as used in this context is a statement about a token's subject. The claims engine can extract claim(s) from one or more different types of security tokens corresponding to the multiple security schemes. These extracted claim(s) can then be selectively mapped to other claims using mapping information that is accessible to the server. The security decision can then be based on the extracted and/or derived claim(s) rather than tokens. This system can thereby support multiple security schemes and simplify the security process for the user.

Generic security claim processing model

A data structure with endpoint address and security information. The data structure includes an address field that includes one or more endpoint addresses for an entity. The data structure further includes a security field that includes one or more keys for facilitating secure communications with the entity. The data structure may also be such that the contents of the address field and the security field are serialized in the data structure. The data structure may be extensible such that new address fields and security fields may be added.

Endpoint identification and security

A web services namespace pertains to an infrastructure for enabling creation of a wide variety of applications. The infrastructure provides a foundation for building message-based applications of various scale and complexity. The infrastructure or framework provides APIs for basic messaging, secure messaging, reliable messaging and transacted messaging. In some embodiments, the associated APIs are factored into a hierarchy of namespaces in a manner that balances utility, usability, extensibility and versionability.

Interface infrastructure for creating and interacting with web services

Growing community of inventors

Redmond, WA, United States of America

Tomasz Janczuk