Originally created by @mprasil on GitHub (Jul 1, 2018).
A call to /api/ciphers/{{cipher-uuid}}/delete-admin throws 404.
Server logs:
POST /api/ciphers/CIPHER_UUID/delete-admin application/json; charset=utf-8:
=> Error: No matching routes for POST /api/ciphers/CIPHER_UUID/delete-admin application/json; charset=utf-8.
=> Warning: Responding with 404 Not Found catcher.
=> Response succeeded.
The POST data is a simple json:
{"id":"CIPHER_UUID"}
I guess we can just use one of the current delete functions to handle this one with some extra checks for admin access.
Originally created by @mprasil on GitHub (Jul 1, 2018).
A call to `/api/ciphers/{{cipher-uuid}}/delete-admin` throws 404.
Server logs:
```
POST /api/ciphers/CIPHER_UUID/delete-admin application/json; charset=utf-8:
=> Error: No matching routes for POST /api/ciphers/CIPHER_UUID/delete-admin application/json; charset=utf-8.
=> Warning: Responding with 404 Not Found catcher.
=> Response succeeded.
```
The POST data is a simple json:
```json
{ "id":"CIPHER_UUID"}
```
I guess we can just use one of the current delete functions to handle this one with some extra checks for admin access.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @mprasil on GitHub (Jul 1, 2018).
A call to
/api/ciphers/{{cipher-uuid}}/delete-adminthrows 404.Server logs:
The POST data is a simple json:
I guess we can just use one of the current delete functions to handle this one with some extra checks for admin access.
@mprasil commented on GitHub (Jul 1, 2018):
Submitted PR #54