Curl command in AEM doesn't work in higher environments with Basic Auth | Community
Skip to main content
R
rakesh_h2
Level 3
June 27, 2023
Solved

Curl command in AEM doesn't work in higher environments with Basic Auth

  • June 27, 2023
  • 4 replies
  • 2786 views

I'm trying to execute curl command to upload a package in higher environments in AEMaaCS by passing Basic Auth.

List of common AEM cURL commands | Adobe Experience Cloud

But it throws an error :

 

 

 

503client read error

 

 

 

I'm passing user credentials as Basic Authentication. No issue related to permissions.

Note: It works when I try in localhost. 

Please help!

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by aanchal-sikka

@rakesh_h2 

 

1. We did with Service Accounts for Servers and credentials for local. You need to set up permissions for the service account, once its configured. 

 

2. Programmatically, we will need HTTP or Curl. In both cases, we are creating packages. The timeout affect both of them. Hence, we have created multiple packages with smaller filters.

 

 

Also, please explore the Content Copy Tool https://experienceleague.adobe.com/docs/experience-manager-cloud-manager/content/using/content-copy.html?lang=en

 

It has been recently released by Adobe for sync from Higher to Lower environments. Vice versa is not allowed

4 replies

EstebanBustamante
Community Advisor and Adobe Champion
EstebanBustamanteCommunity Advisor and Adobe Champion
Community Advisor and Adobe Champion
June 27, 2023

Are you sure the package manager is enabled in the AEMaaCS environment? (Keep in mind that this is usually disabled for prod environments), because It looks like the URL is not available, that's why you are getting 503

Esteban Bustamante
    R
    rakesh_h2Author
    Level 3
    June 27, 2023

    @estebanbustamante The screenshot is of dev author environment's. But I'm able to access prod author's package manager as well. That means curl should work, right?

      krishna_sai
      Community Advisor
      krishna_saiCommunity Advisor
      Community Advisor
      June 27, 2023

      Hi @rakesh_h2 , Can you generate service credentials for your environment and with the help of these credentials you should be able to generate JWT token and exchange it with IMS to get access token.

      you can send this generated access token as a header in curl command
      curl -H "Authorization: Bearer <your_ims_access_token>" https://<environment>/crx/packmgr/service/.json/?cmd=upload

      Hope this helps,
      Krishna

        R
        rakesh_h2Author
        Level 3
        June 27, 2023

        @krishna_sai Thanks for the response. Doesn't it work with Basic Authentication?

          krishna_sai
          Community Advisor
          krishna_saiCommunity Advisor
          Community Advisor
          June 27, 2023

          It should work with basic auth too. It might be possible to get 503 because of timeout
          Just wanted to try the other way round to access the server

            DPrakashRaj
            Community Advisor
            DPrakashRajCommunity Advisor
            Community Advisor
            June 27, 2023

            Please share the curl command that you executed on command line

            with error response

              R
              rakesh_h2Author
              Level 3
              June 28, 2023

              @dprakashraj I tried in CLi with Basic Auth. No error. But its not getting uploaded.

                DPrakashRaj
                Community Advisor
                DPrakashRajCommunity Advisor
                Community Advisor
                June 28, 2023

                Hi Rajesh,

                can you check the file path again. I assume you are on windows machine and path band looks weird to me as all directory are separated by (\\ ) double slash except for the last on which is deprecated by one slash.

                you can also try the curl command by putting the file to the same location from where you are executing it.

                You can also refer to this document for showing the progress https://aemmastery.com/upload-and-install-package-via-curl-6e47898d7b1b

                  aanchal-sikka
                  Community Advisor
                  aanchal-sikkaCommunity Advisor
                  Community Advisor
                  June 28, 2023

                  Hello @rakesh_h2 

                   

                  For any server-to-server or API-based communications, Access tokens is the recommended way.

                   

                  We have also noticed the 503 error recently. It is happening with large packages (caused by a time-out of approx 60 seconds) for CURL or HTTP commands. Mainly, we will observe these for download, build and upload commands.

                   

                  Try creating smaller packages, the Access Token should work.

                  Aanchal Sikka
                    R
                    rakesh_h2Author
                    Level 3
                    June 28, 2023

                    Hi @aanchal-sikka , A few questions:

                    1. CURL doesn't work with Basic Auth at all?

                    2. Even if I try with Access token, it works only for packages with smaller size? If so, what's the recommended way to build or install or upload bigger packages programmatically?

                      aanchal-sikka
                      Community Advisor
                      aanchal-sikkaCommunity AdvisorAccepted solution
                      Community Advisor
                      June 28, 2023

                      @rakesh_h2 

                       

                      1. We did with Service Accounts for Servers and credentials for local. You need to set up permissions for the service account, once its configured. 

                       

                      2. Programmatically, we will need HTTP or Curl. In both cases, we are creating packages. The timeout affect both of them. Hence, we have created multiple packages with smaller filters.

                       

                       

                      Also, please explore the Content Copy Tool https://experienceleague.adobe.com/docs/experience-manager-cloud-manager/content/using/content-copy.html?lang=en

                       

                      It has been recently released by Adobe for sync from Higher to Lower environments. Vice versa is not allowed

                      Aanchal Sikka
                        Terms & ConditionsAccessibility statement

                        Loading footer...