-
Bug
-
Resolution: Unresolved
-
Low
-
7
-
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
-
AX-715 After site rename, old name redirect only works on browser and not any other API
- Gathering Interest
[AX-623] After site rename, REST API calls failing with 401/403/404 response code
Support reference count | New: 7 |
Component/s | Original: Admin - Custom Domains [ 73295 ] | |
Component/s | New: Org Management - App URLs - Custom Domains [ 80135 ] | |
Key | Original: CLOUD-11926 | New: AX-623 |
Support reference count | Original: 13 | |
Project | Original: Atlassian Cloud [ 14613 ] | New: Admin Experience [ 24210 ] |
Support reference count | Original: 12 | New: 13 |
Support reference count | Original: 11 | New: 12 |
Support reference count | Original: 10 | New: 11 |
Support reference count | Original: 9 | New: 10 |
Support reference count | Original: 7 | New: 9 |
Support reference count | Original: 6 | New: 7 |
Support reference count | Original: 5 | New: 6 |
Labels | Original: jsw-s11 | New: RIBS-SHORT jsw-s11 |