IP Library Granted Patent US 10,382,434
Granted Patent B2
US 10,382,434 · App. 15/725,800 · Granted Aug 13, 2019

Actively federated mobile authentication

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,382,434
App. No.
15/725,800
Granted
Aug 13, 2019
Kind
B2
Abstract

To make a trusted web service call, a client application sends a series of messages to obtain tokens that allow service requests to pass through a service relay. The user obtains a first security token by providing the user's credentials. A second token is obtained from a trust broker that validates the first token. Both tokens are then sent with a service request to a service relay. The service relay validates the second token and then passes the first token and the service request to a connector service. The connector service validates the first token and passes the service request to a target back end service. The connector service acts as the user when communicating with the back end service. Service responses are routed back to the user through the connector service and the service relay.

Claims (30)

1. A method performed by a client computing device, the method comprising:

sending a user credential over a computer network to an identity provider having an established trust relationship with a hosted service that is hosted by a computing system that is remote from the client computing device,

the user credential being associated with a user of the client computing device;

receiving, from the identity provider over the computer network, a first token including authentication information configured to authenticate a service request with, the hosted service;

sending the, first token to a trust broker that has an established trust relationship with the identity provider;

receiving, from the trust broker in response to the first token, a second token including a form of authentication information that is different than the first token and is configured to authenticate a service relay to send the service request to the hosted service;

sending, to the service relay, the service request with the second token; and

receiving, from the service relay, a service response indicative of authentication of the client computing device by the hosted service based on the second token.

2. The method of claim 1 , wherein the hosted service comprises a firewall-protected network that is protected by a firewall, and the service relay is configured to communicate across the firewall.

3. The method of claim 1 , wherein the hosted service comprises an enterprise service.

4. The method of claim 1 , wherein the client computing device comprises a mobile device.

5. A client computing device comprising:

a processor; and

memory storing instructions executable by the processor, wherein the instructions, when executed, configure the client computing device to:

send a user credential over a computer network to an identity provider having an established trust relationship with a hosted service, that is hosted by a system that is remote from the client computing, device;

receive, from the identity provider, a first token including authentication information configured to authenticate a service request with the hosted, service;

send, to a service relay, the service request with the first token; and

receive, from the service relay, a service response indicative of authentication of the client computing device by the hosted service based on the first token.

6. The client computing device, of claim 5 , wherein the hosted service comprises a firewall-protected network that is protected by a firewall, and the service relay is configured to communicate across the firewall.

7. The client computing device of claim 5 , wherein the hosted service comprises an enterprise service.

8. The client computing device of claim 7 , wherein the enterprise service comprises at least one of:

a back office service configured to, process the service request: or

a connector service configured to expose a web service endpoint for a back office service.

9. The client computing device of claim 5 , wherein the instructions, when executed, configure the client computing device to:

send the first token to a trust broker that has an established trust relationship with the identity provider;

receive, from the trust broker in response to the first token, a second token including an additional form of authentication information that is different than the first token and is configured to authenticate a service relay to send the service request and the first token to the hosted service; and

send, to the service relay, the service request with both the first token and the second token.

10. The client computing device of claim 5 , wherein the client computing device comprises a mobile device.

11. The Client computing device of claim 5 , wherein the hosted service comprises a connector service configured to extract user identity information from the first token.

12. The client computing device of claim 5 , wherein the hosted service comprises a group of different systems configured to provide one or more services.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 23, 2018
From: YOUNG, KYLE STAPLEY; DROLLINGER, ROBERT ARON; O'BRIEN, ROBERT; RUNDE, DAVID J.; PANDYA, JAGRUTI DUSHYANT; EL KHOURY, GEORGES
To: MICROSOFT CORPORATION
Reel/Frame 045613/0471 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 23, 2018
From: MICROSOFT CORPORATION
To: MICROSOFT TECHNOLOGY LICENSING, LLC
Reel/Frame 045613/0515 →