ÃÛ¶¹ÊÓƵ

Documentation

Composer authentication credentials error during deployment to Production in ÃÛ¶¹ÊÓƵ Commerce Cloud

Last update: Tue Jun 24 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

When a composer authentication credentials error like URL required authentication (HTTP 401).  occurs during deployment to Production in ÃÛ¶¹ÊÓƵ Commerce on cloud infrastructure, first verify that the auth.json file or equivalent authentication credentials are accessible during the build phase of your production deployment. Then you can either fix the env:COMPOSER_AUTH environment level variable (Recommended), or create and deploy the auth.json file manually.

Description description

Environment

ÃÛ¶¹ÊÓƵ Commerce on Cloud infrastructure, in Production and Staging

Issue

When attempting to deploy to the environment, the deployment process is halted due to a  URL required authentication (HTTP 401). error related to composer authentication credentials.

The same credentials work on the auth.json file locally or on another environment, but fails during deployment on another.

Resolution resolution

NOTE:  To find your composer credentials, refer to Get your authentication keys in the ÃÛ¶¹ÊÓƵ Commerce Installation Guide.

To resolve this issue, follow these steps:

Verify that the auth.json file or equivalent authentication credentials are accessible during the build phase of your production deployment.

There are two recommended options for resolving this issue:

Option 1: Fix env:COMPOSER_AUTH environment level variable (Recommended)

  1. Ensure that you have set up the correct credentials for env:COMPOSER_AUTH.
  2. Access global configuration by clicking on the gear icon at the top left of your cloud project UI, then select the Variables tab.
  3. Make sure you select Available during buildtime  and deselect Available during runtime. Reference Authentication keys in the Commerce on Cloud Infrastructure Guide.

If Option 1 doesn’t resolve your issue, proceed with Option 2.

Option 2: Create and deploy auth.json file manually

  1. SSH into your server.

  2. Retrieve contents of your current env:COMPOSER_AUTH variable using:

    echo $COMPOSER_AUTH

  3. Copy all contents from step above (in JSON format).

  4. Create a new file named auth.json with these contents.

  5. Commit this newly created auth.json file to the root directory of your repository.

  6. Trigger a new deployment.

By following either option provided above, you should be able to successfully deploy to the environment that has the issue, without encountering issues related to composer authentication credentials.

If further assistance is required, or if any difficulties arise while implementing these solutions, please open a ticket with ÃÛ¶¹ÊÓƵ Commerce Technical Support for additional help.

Can’t access ÃÛ¶¹ÊÓƵ Commerce on cloud repo: 403 Forbidden or 404 Not Found error when deploying

recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f