Microsoft Technology Licensing, LLC

Oren Jordan Melzer

Anirban Basu

Caleb Geoffrey Baker

Violet Anna Barhudarian

Jiangfeng Lu

Victor Boctor

Kamen Kamenov Moutafov

Yordan Ivanov Rouskov

Radhika Kashyap

William Bruce Barr, Iii

Shuang Lu

Sarvani Kumar Bhamidipati

Ariel Nicolas Gordon

Michael B Jones

Arun K Nanda

Murli D Satagopan

Pui-Yin Winfred Wong

Charles Ronald Reeves, Jr

Carlos Adrian Lopez Castro

Chandra Sekhar Surapaneni

Praveen Erode Murugesan

Nitika Gupta

Randeep Singh

William Bruce Iii Barr

Murli Dharan Satagopan

A system for authenticating a principal comprises first and second authentication systems and an authentication artifact signing service. The first authentication system issues a request comprising an authentication artifact associated with the principal and a specification of one or more modifications to be made thereto, the authentication artifact being generated by a second authentication system, signed thereby using a key, and stored by the first authentication system. The signing service receives the request and, responsive thereto: applies the modification(s) to the authentication artifact to generate a modified authentication artifact, signs the modified authentication artifact using a key of the second authentication system, and returns the signed modified authentication artifact to the first authentication system for use in authenticating the principal. The first authentication system executes in a different security domain than the signing service and is unable to access the key used thereby.

Secure authentication artifact signing service for authentication system

Techniques are described herein that are capable of dynamically routing an authentication request to a backup authentication system by a client device. For instance, the client device stores a list, which identifies authentication systems that are authorized to respond to authentication requests from the client device. The client device sends the authentication request toward a primary authentication system based at least in part on the authentication request identifying the primary authentication system as a recipient of the authentication request. The authentication request requests authentication of a principal by the primary authentication system. The client device causes the backup authentication system to authenticate the principal using an authentication package received from the primary authentication system by dynamically routing the authentication request to the backup authentication system based at least in part on not receiving a valid response to the authentication request and further based at least in part on the list.

Client device capable of dynamically routing authentication requests to a backup authentication system

Techniques are described herein that are capable of dynamically failing over authentication traffic to a backup authentication system by a proxy system. An authentication request, which requests authentication of a principal, is received at the proxy system. The authentication request is directed to a primary authentication system. A determination is made, by the proxy system, that the primary authentication system is incapable of providing a valid response to the authentication request. The backup authentication system is caused, by the proxy system, to authenticate the principal using an authentication package received from the primary authentication system by dynamically routing the authentication request to the backup authentication system as a result of the primary authentication system being incapable of providing a valid response to the authentication request.

Proxy configured to dynamically failover authentication traffic to a backup authentication system

Techniques are described herein that are capable of using an authentication package from a primary authentication system to authenticate a principal by a backup authentication system. The authentication package includes an authentication artifact, which is signed with a cryptographic key by the primary authentication system and which includes claim(s) that are usable to authenticate the principal, and further includes metadata. The metadata includes credential verification information that is usable to verify a credential of the principal and a first principal identifier that identifies the principal. A request to authenticate the principal is received at the backup authentication system. The request includes the credential and a second principal identifier that identifies the principal. The principal is authenticated by the backup authentication system by verifying the credential using the credential verification information and further by determining that the first principal identifier corresponds to the second principal identifier.

Backup authentication system configured to use an authentication package from a primary authentication system to authenticate a principal

A computing system configured to support entities having the ability to indicate capability information for capabilities of the entities is illustrated. Embodiments may include an identity provider computer system comprising at least one processor. The identity provider computer system is configured to receive requests for access tokens from entities. The requests include capability information for the entities. The identity provider computer system is further configured to provide access tokens to the entities which include the capability information. The computing system further includes a resource provider computer system comprising at least one processor configured to receive resource requests and access tokens from entities. The access tokens include the capability information. The resource providers are further configured to provide responses to the entities according to the capability information.

Client readiness system

Authenticating computing entities. A method includes at an identity provider, providing a first access token to an entity for use by the entity in obtaining resources from a resource provider. The method further includes, at the identity provider, receiving response information from the entity. The response information from the entity is provided to the entity from the resource provider as a result of the resource provider enforcing policy at the resource provider. At the identity provider, a second access token is provided to the entity. The second access token is provided based on the response information, such that the second access token can be used by the entity to obtain the resources from the resource provider.

Rich token rejection system

Managing an authenticated user session. A method includes a resource provider computer system subscribing to a conditional access termination service for an entity configured to obtain resources from the resource provider computer system through a user session. The resource provider computer system receives an event, related to resource requests, for the entity from the conditional access termination service. The resource provider computer system receives a request for resources from the entity. The resource provider computer system evaluates the request with respect to the event. The resource provider computer system responds to the request based on evaluating the request with respect to the event.

Instant enforcement of centrally configured IT policies

An embodiment disclosed herein is related to computing systems and method for a computing system to generate an access token that includes an IP address from a request. In the embodiment, a request is received for access to one secured data items. The request may include user credentials that specify that a user making the request is permitted to access the secured data items. The user credentials are validated and an Internet Protocol (IP) address that the request was sent from is determined. An access token is generated that includes the IP address that the request was sent from.

Using IP heuristics to protect access tokens from theft and replay

Described is using a client-side account selector in a passive authentication protocol environment (such as OpenID) in which a relying party website trusts the authentication response from an identity provider website. The account selector may access and maintain historical information so as to provide user-specific identity provider selection options (rather than only general identity provider selection options). The account selector is invoked based upon an object tag in the page, e.g., as invoked by a browser extension associated with that particular object tag. The account selector may communicate with a reputation service to obtain reputation information corresponding to the identity providers, and vary its operation based upon the reputation information.

Growing community of inventors

Redmond, WA, United States of America

Oren Jordan Melzer