Microsoft Technology Licensing, LLC

William Bruce Barr, Iii

Caleb Geoffrey Baker

Radhika Kashyap

Yordan Ivanov Rouskov

Oren Jordan Melzer

Violet Anna Barhudarian

Anirban Basu

Jiangfeng Lu

Carlos Adrian Lopez Castro

Pui-Yin Winfred Wong

Christopher Adam Brooks

Stuart Kwan

Svyatoslav Trukhanov

Zhifeng Wang

Adam Edwards

Arturo Huato Lucatero

Abhijeet Kumar Sinha

Generally discussed herein are devices, systems, and methods for adaptive authorization using a local route as a named location. A method can include defining a local route and a corresponding local route endpoint, associating a compute resource as a destination of the local route endpoint, defining an adaptive authorization policy that limits access to the compute resource to be through the local route endpoint, and enforcing access to the compute resource based on the defined adaptive authorization policy.

Adaptive authorization with local route identifier

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

A CRL can be divided into a number of segments. The number of segments into which the CRL is divided can be determined by using a predefined number of serial numbers per segment. The segment in which a particular certificate is included can be determined by application of a consistent hashing algorithm to the serial number of the certificate to determine in which segment the serial number will be found if revoked, thereby increasing the efficiency of determining the revocation status of the certificate. Metadata common to each CRL can be cached on each server and on the remote cache. The segments themselves can be cached in the remote cache. Storing the segments only in the remote cache decreases resource consumption (e.g., amount of memory used in the local cache). Storing the segments in the remote cache enables optimization for locality.

Efficient certificate revocation list validation in multi-tenant cloud services

Growing community of inventors

Issaquah, WA, United States of America

William Bruce Barr, Iii