-
Bug
-
Resolution: Unresolved
-
Low
-
12
-
Minor
-
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
- Rename site "randomsite1234.atlassian.net" to "changedsite1234.atlassian.net"
- Make a REST call to an API endpoint
- https://randomsite1234.atlassian.net/rest/api/2/myself
- https://randomsite1234.atlassian.net/wiki/rest/api/content
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
- is related to
-
ACCESS-1779 After site rename, old name redirect only works on browser and not any other API
- Gathering Interest