Getting 403 when POSTing to /bin/dxml/upgrade/3xto4x | Community
Skip to main content
M
MarkBo
March 11, 2022

Getting 403 when POSTing to /bin/dxml/upgrade/3xto4x

  • March 11, 2022
  • 1 reply
  • 1088 views

I'm following the instructions for upgrading to XML Doc 4.0, and when I get to the point of doing the POST to /bin/dxml/upgrade/3xto4x I get a "403 Forbidden" response. My GET to /bin/dxml/upgrade/3xto4x/report worked fine, and the report included:

 "upgradeStatus": {
"status": "MIGRATION_POSSIBLE",
"message": "You can start the migration activity"
}

I've tried specifying my (admin-level) username and password to the REST client as Basic Authentication, but to no avail.

 

What am I doing wrong here?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

1 reply

Jineet_Vora
Community Advisor and Adobe Champion
Jineet_VoraCommunity Advisor and Adobe Champion
Community Advisor and Adobe Champion
March 11, 2022

Hi @markbo,

How are you making the POST request? Are you using cURL or Postman? Also, are you making the request with admin credentials? Looks like your request is not having appropriate permissions to fulfil the request.

 

I tried using the below cURL command and it worked:

 

curl -u admin:admin -X POST http://localhost:4502/bin/dxml/upgrade/3xto4x

 

 

    M
    MarkBoAuthor
    March 11, 2022

    Thank you for your reply, @jineet_vora.

     

    I'm using the RESTClient plugin for Firefox. That addon helpfully outputs the equivalent `curl` command for the requests it sends. The curl command it provides in this case is:

    curl -X POST -H 'Authorization: Basic XXXXXX' -i 'http://test-aem.company.com:4502/bin/dxml/upgrade/3xto4x'

    (Note that I have replaced the real auth string with "XXXXXX" for posting here.)

     

    When I run that command (now that I've read up on it and understand it better), it works fine. Until I can get the plugin to show me the HTTP of the request it's sending, I don't see a way to debug further. I'll just have to use curl.

      Terms & ConditionsAccessibility statement

      Loading footer...