ClearOS Bug Tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0022461ClearOSclearos-frameworkpublic2018-11-21 10:332019-02-23 16:27
Assigned Todloper 
PrioritynormalSeverityfeatureReproducibilityhave not tried
PlatformOSOS Version
Product Version 
Target Version7.6.0 UpdatesFixed in Version 
Summary0022461: Add new standard Exceptions/REST responses
DescriptionThere will be some circumstances where an API request will need to send a "not capable" error message. Consider the case of updating a user's profile:

- REST: POST /api/v1/user/cindy
- API: user->update()

If using the Active Directory connector, no updates/writes are allowed for users -- AD handles that. The REST response and exception should return this standard "not capable" error. Clients can then handle the specific issue if desired.
TagsNo tags attached.
Attached Files

- Relationships

-  Notes
dloper (administrator)
2019-02-23 16:27

Migrated to: [^]

- Issue History
Date Modified Username Field Change
2018-11-21 10:33 user2 New Issue
2018-11-21 10:34 user2 Status new => confirmed
2019-02-23 16:27 dloper Note Added: 0009581
2019-02-23 16:27 dloper Status confirmed => closed
2019-02-23 16:27 dloper Assigned To => dloper
2019-02-23 16:27 dloper Resolution open => suspended