Table 1. Response Parameter
| Response Parameter |
Style |
Type |
Description |
| None |
|
|
|
Table 2. HTTP Response Code
| HTTP Response Code |
Description |
| 204 No Content |
Successful request |
| 400 Bad Request |
Request does not comply with specification |
| 401 Unauthorized |
The provided token is not valid or cannot be verified |
| 403 Forbidden |
The provided token although valid, does not provide appropriate permissions to the
user |
| 404 Not Found |
No such user or storage account exists |
| 405 Method Not Allowed |
Although the user may be valid, the user does not have privileges to access storage
account |
| 503 Service Unavailable |
The credential API service is currently unavailable |
Table 3. Role Guidance
| Role Guidance |
Description |
| Key Management Admin Permission |
Generic permission to allow an admin to manage access keys |
| Key Management User Permission |
Generic permission to allow a user to manage access keys |
Example Output
Request
---------
DELETE <accesser>:8338/credentials/a42a27755ce6442596b049bd7dd8a563
Response
---------
HTTP/1.1 204 OK
Content-Length: 0
Accept-Ranges: bytes
Content-Type: application/json; charset=utf-8
X-Timestamp: 1458262564.22774
X-Trans-Id: tx8ea13a3a835544d8bebf1-0056eb522a
This operation does not send a request body and does not return a response body