Uploaded image for project: 'Crowd'
  1. Crowd
  2. CWD-5690

Do not allow the Crowd API to respond 204 or success when a updating a field has not changed any details

    XMLWordPrintable

    Details

    • Type: Suggestion
    • Status: Gathering Interest (View Workflow)
    • Resolution: Unresolved
    • Fix Version/s: None
    • Component/s: REST
    • Labels:
      None
    • Feedback Policy:

      Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Description

      When you make a call to such as below with NULL user details for the user which is not allowed:

      PUT /rest/usermanagement/latest/user?username=example-user
      body: {"name": "example-user", "first-name": "", "last-name": "example service account", "email": "", "display-name": "example service account", "active": true, "password": {"value": "dont-care-it-authenticates-from-ad-anyway"}}
      

      That call will respond with a 204 success even though the fields have not been updated which can be confusing when scripting or automating users indicating the call has been a success when technically it hasn't. In the UI you are warned these fields are required.

      It would be beneficial to have a different response when a required field or invalid character is included and the field is not updated with a warning of some description or a 415 etc.

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            dmark@atlassian.com Danny
            Votes:
            2 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated: