Find User Consent's
get
/oam/services/rest/consent
The REST API enables Administrator to fetch consents related to a User. The API return's all the consents for a given User or specific consents for a given User, OAuth Client and OAuth Application combination.
Request
Supported Media Types
- application/x-www-form-urlencoded
Query Parameters
-
clientIdentifier: string
OAuth Client ID/Identifier
-
resServerId: string
OAuth Application ID/Identifier
-
userId(required): string
User name/identifier who's consents needs to be retrieved.
Header Parameters
-
authorization(required): string
Base64 encoded header of Administrator:Secret. This is an authentication mechanism for weblogic Administrator to access resource.
-
x-oauth-identity-domain-name(required): string
OAuth Identity Domain name under which user consents are expected.
Response
Supported Media Types
- application/json
200 Response
Sucessfully retrieved user consent - detail
Nested Schema : consent
Type:
Show Source
object
-
clientId(required):
string
OAuth Client Identifier
-
consentId(required):
string
OAuth Consent Unique Identifier
-
createTimeStamp(required):
string
Creation timestamp for OAuth Consent
-
resourceId(required):
string
OAuth Application Identifier
-
scopes(required):
array scope
-
valid(required):
boolean
Flag to identify OAuth Consent validity. True - Consent is valid, False - Consent is In-valid
400 Response
Failed to retrieve user consent - detail
Root Schema : schema
Type:
Show Source
object
-
error:
string
Error code
-
error_description:
string
Error description
Example:
{
"error":"400",
"error_description":"Required parameter 'X-OAUTH-IDENTITY-DOMAIN-NAME' is not present."
}
Examples
The following example shows a sample request and response to fetch all the consents for a specific user, under an OAuth Identity Domain Name.
cURL Example to Fetch All the Consents
curl --location --request GET 'https://<AdminServerHost:AdminServerPort>/oam/services/rest/consent?userId=DemoUser' \ --header 'X-OAUTH-IDENTITY-DOMAIN-NAME: DemoDomain' \ --header 'Authorization: Basic d2VibG9naWM6d2VsY29tZTE='
Sample Response
{ "consents": [ { "clientId": "DemoClient", "consentId": "ebe683b9-0345-3c35-a21d-35e57958ed21", "createTimeStamp": "Wed Apr 08 22:12:15 PDT 2020", "resourceId": "506a50c2-a892-49ee-85ad-9993169a18bf", "scopes": [ "DemoResource.editDemoRes", "DemoResource.delDemoRes", "DemoResource.viewDemoRes" ], "valid": true }, { "clientId": "DemoClient", "consentId": "8c1d5d3a-dc74-3939-aa72-03c12fcff3b3", "createTimeStamp": "Wed Apr 08 22:12:15 PDT 2020", "resourceId": "OPENID_MGMT_RESOURCE", "scopes": [ "openid", "profile", "email" ], "valid": true } ] }
The following example shows a sample request and response to fetch consents for each user and client-application.
cURL Command to Fetch Consents for Each User and Client-Application
curl --location --request GET 'https://<AdminServerHost:AdminServerPort>/oam/services/rest/consent?userId=DemoUser&clientIdentifier=DemoClient&resServerId=506a50c2-a892-49ee-85ad-9993169a18bf' \ --header 'X-OAUTH-IDENTITY-DOMAIN-NAME: DemoDomain' \ --header 'Authorization: Basic d2VibG9naWM6d2VsY29tZTE='
Sample Response
{ "consents": [ { "clientId": "DemoClient", "consentId": "ebe683b9-0345-3c35-a21d-35e57958ed21", "createTimeStamp": "Wed Apr 08 22:12:15 PDT 2020", "resourceId": "506a50c2-a892-49ee-85ad-9993169a18bf", "scopes": [ "DemoResource.editDemoRes", "DemoResource.delDemoRes", "DemoResource.viewDemoRes" ], "valid": true } ] }