Uploaded image for project: 'Confluence Cloud'
  1. Confluence Cloud
  2. CONFCLOUD-76099

Getting space permissions through the REST API intermittently returns wrong user data

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Low
    • User - Profile
    • None

    Description

      Issue Summary

      When using the GET space endpoint and setting the expand option as permissions, we sometimes see wrong and inconsistent user information.

      This issue is intermittent and does not reproduce most of the time but when it does, it can easily introduce unwanted data and create inconsistencies on automation that are relying on this endpoint.

      We haven't confirmed if the same behaviour can be observed on the V2 endpoint

      Steps to Reproduce

      1. Perform a GET space REST API call:
      /wiki/rest/api/space/{spaceKey}?expand=permissions 

      Expected Results

      User information gets returned properly on the REST API call response

      {
        "type": "known",
        "accountId": "user_aaid_here",
        "accountType": "",
        "email": "",
        "publicName": "Full user information", // <--- Affected value
        "profilePicture": {
          "path": "/wiki/aa-avatar/user_aaid_here",
          "width": 48,
          "height": 48,
          "isDefault": false
        },
        "displayName": "Full user information", // <!--- Affected value
        "isExternalCollaborator": false,
        "_expandable": {
          "operations": "",
          "personalSpace": ""
        },
        "_links": {
          "self": "https://instance.atlassian.net/wiki/rest/api/user?accountId=user_aaid_here"
        }
      } 

      Actual Results

      The following exception gets thrown:

      java.util.concurrent.ExecutionException : java.net.SocketTimeoutException: 300 milliseconds timeout on connection http-outgoing-189 [ACTIVE] : 300 milliseconds timeout on connection http-outgoing-189 [ACTIVE] 

      Failing with the error message:

      User Profile : Couldn't request user profile 

      End result is that user information gets truncated on the result of the API call.

      {
        "type": "known",
        "accountId": "user_aaid_here",
        "accountType": "",
        "email": "",
        "publicName": "User xxxx_random_truncated_aaid", // <---- This information is wrong
        "profilePicture": {
          "path": "/wiki/aa-avatar/user_aaid_here",
          "width": 48,
          "height": 48,
          "isDefault": false
        },
        "displayName": "User xxxx_random_truncated_aaid", // <---- This information is wrong
        "isExternalCollaborator": false,
        "_expandable": {
          "operations": "",
          "personalSpace": ""
        },
        "_links": {
          "self": "https://instance.atlassian.net/wiki/rest/api/user?accountId=user_aaid_here"
        }
      } 

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              c5522313772a Julian
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated: