Microsoft Technology Licensing, LLC

Haibo Luo

Raja Krishnaswamy

Vadim Eydelman

Matthias Adam Leibmann

Thottam Sriram

Brian Kress

Shrikrishna Vijaykumar Borde

Shawn Farkas

Lei Yu

Michael D Downen

Moustafa Noureddine

Chris King

Online and on-premise applications identify trusted authentication providers. The applications are configured with a list of trusted issuers of authentication credentials. When an application receives a request requiring authentication, the application returns a 401 response that includes the trusted issuer list. The requesting application compares the trusted issuer list from the 401 response to its own list of authentication providers. If there is a match between the two lists, then the requesting application creates a self-issued token for the authentication provider. The authentication provider uses the self-issued token to generate an authentication token for the requesting application. The requesting application may also directly create a token for a target partner application, without an authentication provider, if there is a direct trust between the two applications.

Integrating server applications with multiple authentication providers

Various technologies and techniques are disclosed that use code access security for providing runtime accessibility checks. A request is received from a first program to access at least one private member of a second program at runtime. If the first program has a greater than or equal security context than the second program, then the first program is granted access to the at least one private member of the second program. This code access security check can be provided in a framework environment that is responsible for managing programs that are from unknown or untrusted sources.

Using code access security for runtime accessibility checks

Growing community of inventors

Kirkland, WA, United States of America

Haibo Luo