Dynamically mapping users to groups
US-2015156190-A1 · Jun 4, 2015 · US
US9860234B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9860234-B2 |
| Application number | US-201715640311-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jun 30, 2017 |
| Priority date | Sep 20, 2013 |
| Publication date | Jan 2, 2018 |
| Grant date | Jan 2, 2018 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A framework, which conforms to the OAuth standard, involves a generic OAuth authorization server that can be used by multiple resource servers in order to ensure that access to resources stored on those resource servers is limited to access to which the resource owner consents. Each resource server registers, with the OAuth authorization server, metadata for that resource server, indicating scopes that are recognized by the resource server. The OAuth authorization server refers to this metadata when requesting consent from a resource owner on behalf of a client application, so that the consent will be of an appropriate scope. The OAuth authorization server refers to this metadata when constructing an access token to provide to the client application for use in accessing the resources on the resource server. The OAuth authorization server uses this metadata to map issued access tokens to the scopes to which those access tokens grant access.
Opening claim text (preview).
What is claimed is: 1. A computer-implemented method comprising: based on a request by an application for access to a first service and for access to a second service, obtaining, at a computer system of an authorization system, from a first server computer that provides the first service, a first scope of access information for the application to access the first service requested by the application, wherein the first scope of access information is determined by the first server computer applying a first policy to one or more attributes associated with an identity of the application provided by the computer system to the first server computer; based on the request by the application for the first service and the second service, obtaining, at the computer system, from a second server computer that provides the second service, a second scope of access information for the application to access the second service requested by the application, wherein the second scope of access information is determined by the second server computer by applying a second policy to the one or more attributes associated with the identity of the application provided by the computer system to the second server computer; and sending, by the computer system, to the application, a token that indicates access to the first service and access to the second service, wherein the token indicates the access to the first service based on the first scope of access information obtained from the first server computer, and wherein the token indicates the access to the second service based on the second scope of access information obtained from the second server computer. 2. The computer-implemented method of claim 1 , further comprising: receiving, at the computer system, the request by the application for access to the first service. 3. The computer-implemented method of claim 1 , wherein the first server computer is distinct from the second server computer, and wherein the first service is distinct from the second service. 4. The computer-implemented method of claim 1 , wherein the first service is a first type of service and the second service is a second type of service. 5. The computer-implemented method of claim 1 , wherein the first scope of access information indicates the application is permitted to access the first service, and wherein the second scope of access information indicates the application is not permitted to access the second service. 6. The computer-implemented method of claim 1 , further comprising: determining, by the computer system, from a plurality of server computers, the first server computer that provides access to the first service; and determining, by the computer system, from a plurality of server computers, the second server computer that provides access to the second service. 7. The computer-implemented method of claim 1 , wherein obtaining the first scope of access information from the first server computer includes: providing, by the computer system, the identity of the application to the first server computer, wherein the first server computer determines the first scope of access information using the identity of the application sent to the first server computer; and receiving, by the computer system, from the first server computer, the first scope of access information determined by the first server computer. 8. The computer-implemented method of claim 1 , further comprising: generating, by the computer system, the token; adding the first scope of access information to the token; and adding the second scope of access information to the token. 9. The computer-implemented method of claim 1 , wherein the token is generated before the first scope of access information is obtained and before the second scope of access information is obtained. 10. The computer-implemented method of claim 1 , wherein the request includes an attribute of a user operating the application to access to the first service and to access the second service, and wherein the first policy is further applied to the attribute of the user to determine the first scope of access information. 11. The computer-implemented method of claim 1 , further comprising: identifying, in the request, each of the first service and the second service. 12. A system comprising: one or more processors; and a memory accessible to the one or more processors, the memory storing one or more instructions which, upon execution by the one or more processors, causes the one or more processors to: based on a request by an application for access to a first service and for access to a second service, obtain, by an authorization system, from a first server computer that provides the first service, a first scope of access information for the application to access the first service requested by the application, wherein the first scope of access information is determined by the first server computer applying a first policy to one or more attributes associated with an identity of the application provided to the first server computer; based on the request by the application for the first service and the second service, obtain, by the authorization system, from a second server computer that provides the second service, a second scope of access information for the application to access the second service requested by the application, wherein the second scope of access information is determined by the second server computer by applying a second policy to the one or more attributes associated with the identity of the application provided to the second server computer; and send, by the authorization system, to the application, a token that indicates access to the first service and access to the second service, wherein the token indicates the access to the first service based on the first scope of access information obtained from the first server computer, and wherein the token indicates the access to the second service based on the second scope of access information obtained from the second server computer. 13. The system of claim 12 , wherein the one or more instructions which, upon execution by the one or more processors, further causes the one or more processors to: receive the request by the application for access to the first service. 14. The system of claim 12 , wherein the first server computer is distinct from the second server computer, and wherein the first service is distinct from the second service. 15. The system of claim 12 , wherein the one or more instructions which, upon execution by the one or more processors, further causes the one or more processors to: provide the identity of the application to the first server computer, wherein the first server computer determines the first scope of access information using the identity of the application sent to the first server computer; and receive from the first server computer, the first scope of access information determined by the first server computer. 16. The system of claim 12 , wherein the one or more instructions which, upon execution by the one or more processors, further causes the one or more processors to: generate the token; add the first scope of access information to the token; and add the second scope of access information to the token. 17. A non-transitory computer-readable storage medium comprising, one or more instructions which, upon execution by one or more processors, causes the one or more processors to: based on a request by an application for access to a first service and for access to a second service, obtain, at a computer system of an authorization system, from a f
for controlling access to devices or network resources · CPC title
Entity profiles · CPC title
providing single-sign-on or federations · CPC title
for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32) · CPC title
involving negotiation or determination of the one or more network security mechanisms to be used, e.g. by negotiation between the client and the server or between peers or by selection according to the capabilities of the entities involved (negotiation of communication capabilities H04L69/24) · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.