access_token
is passed, only the access_token
will be revoked. If a refresh_token
is passed, both the refresh_token
and its associated access_token
will be revoked.POST
/oauth2/revoke
application/x-www-form-urlencoded
POST /oauth2/revoke HTTP/1.1Host: sample.portal.tencentciam.comContent-Type: application/x-www-form-urlencodedclient_id=TENANT_CLIENT_ID&client_secret=TENANT_CLIENT_SECRET&token=MOCK_ACCESS_TOKEN
Parameter | Optional | Description |
client_id | false | The client_id of the application. This should be the same as the one used for getting the authorization code and Token. |
client_secret | false | The client_secret of the application. It can be viewed on the basic information page of the application on the Customer Identity Access Management (CIAM) console. |
token | false | The value of access_token or refresh_token . |
HTTP/1.1 200 OK
client_id
is not the same as the one used for initiating login and getting the Token.HTTP/1.1 401 UnauthorizedContent-Type: application/json;charset=UTF-8{"error" : "invalid_client"}
Was this page helpful?