Uploaded image for project: 'Atlassian Cloud'
  1. Atlassian Cloud
  2. CLOUD-11926

After site rename, REST API calls failing with 401/403/404 response code

XMLWordPrintable

      Issue Summary

      After a site rename, if we try to perform a call via REST API call the request will fail with 401 "Client must be authenticated to access this resource."

      Steps to Reproduce

      1. Rename site "randomsite1234.atlassian.net" to "changedsite1234.atlassian.net"
      2. Make a REST call to an API endpoint
      curl -u EMAIL:APITOKEN "https://randomsite1234.atlassian.net/rest/api/2/myself"

      Expected Results

      The REST API call should succeed with 200 HTTP response code

      Actual Results

      The REST API call will fail with a 401/ 403 /404 HTTP response code

      Workaround

      Use the new site name in the REST API call

            [CLOUD-11926] After site rename, REST API calls failing with 401/403/404 response code

            Rune Rasmussen added a comment -

            After merging two cloud sites we need to update the site URL to actually be our company name.
            We have integrations with external systems and Jira/Confluence automations using the APIs to make up for shortcomings in automation actions.

            What should have been a simple job has become a sizable exercise in coordination.

            Rune Rasmussen added a comment - After merging two cloud sites we need to update the site URL to actually be our company name. We have integrations with external systems and Jira/Confluence automations using the APIs to make up for shortcomings in automation actions. What should have been a simple job has become a sizable exercise in coordination.

              Unassigned Unassigned
              pferreira@atlassian.com Paulo F. (Inactive)
              Affected customers:
              6 This affects my team
              Watchers:
              18 Start watching this issue

                Created:
                Updated: