|
Response | createResource ( @HeaderParam("Authorization") String authorization, @ApiParam(value="Resource description", required=true) UmaResource resource) |
|
Response | updateResource (@HeaderParam("Authorization") String authorization, @PathParam("rsid") @ApiParam(value="Resource description ID", required=true) String rsid, @ApiParam(value="Resource description JSON object", required=true) UmaResource resource) |
|
Response | getResource ( @HeaderParam("Authorization") String authorization, @PathParam("rsid") @ApiParam(value="Resource description object ID", required=true) String rsid) |
|
List< String > | getResourceList ( @HeaderParam("Authorization") String authorization, @QueryParam("scope") @ApiParam(value="Scope uri", required=false) String scope) |
|
Response | deleteResource ( @HeaderParam("Authorization") String authorization, @PathParam("rsid") @ApiParam(value="Resource description ID", required=true) String rsid) |
|
Response | unsupportedHeadMethod () |
|
Response | unsupportedOptionsMethod () |
|
The API available at the resource registration endpoint enables the resource server to put resources under the protection of an authorization server on behalf of the resource owner and manage them over time. Protection of a resource at the authorization server begins on successful registration and ends on successful deregistration.
The resource server uses a RESTful API at the authorization server's resource registration endpoint to create, read, update, and delete resource descriptions, along with retrieving lists of such descriptions. The descriptions consist of JSON documents that are maintained as web resources at the authorization server. (Note carefully the similar but distinct senses in which the word "resource" is used in this section.)
- 著者
- Yuriy Zabrovarnyy
-
Yuriy Movchan Date: 02/12/2015