Microsoft Technology Licensing, LLC

Kaushik Raj

Rolando Jimenez Salgado

Rahul Kapoor

Satish Ramchandra Thatte

Arshish C Kapadia

Tarkan Sevilmis

David Koronthaly

Targo Tennisberg

Mohammed Nazeeruddin

Xiaoyu Wu

Javier Dalzell

Sundar Paranthaman

Saji Varkey

Claim based identities are transformed to a set of credentials and securely stored in a secure data store using a number of encryption schemes. The credentials are then used to authenticate applications requiring specific credential types. For each call to the secure store system, a client application may provide a claims token issued by a trusted source, which is used to search for corresponding credentials in the secure data store if the credentials have been created previously for the user.

Transforming claim based identities to credential based identities

Architecture for uninterrupted access to business data by enabling work on rich client machines to be stored in a local business data cache that is always available. A dispatching mechanism executes read/write requests against the local cache transparently to a client application, an automatic synchronization mechanism propagates changes bi-directionally when the client goes online and a live connection with the corresponding backend data source is available. A declarative data access model is employed based on operation stereotyping and grouping that enables client applications to transparently execute create, read, update, delete, query (CRUDQ) and association operations against the local cache as if executed against the actual business data source. The architecture supports the offline creation of entities and sets of related entities when the entity identifiers are generated by the business data source and offline navigation of entity associations when foreign keys are not present in the related entities.

Business data access client for online/offline client use

Versioning and concurrency control architecture of data operations on data of a data source by multiple independent clients of a user. Data operation messages between the clients and the data source are intercepted and tracked for serialization control to a data view instance of the data source. The architecture can be located as an always-on centrally-located system (e.g., mid-tier), accommodate data operations that include create, read, update, delete, and query (CRUDQ) against data sources, and provides support for distributed transactions, locking, versioning, and reliable messaging, for example, for data sources that do not expose such capabilities. A hash is employed for version control and to control changes at the data source. The central system also provides logic for the individual CRUDQ operations, and granular error classification to enable retries whenever possible.

Versioning and concurrency control for multiple client access of data

Growing community of inventors

Issaquah, WA, United States of America

Kaushik Raj