---
title: "Why do I get HTTP Basic: Access denied during Automatic Updates or Composer Update?"
date: "2026-06-05T06:22:32+00:00"
summary:
image:
type: "article"
url: "/acquia-cloud-platform/add-ons/code-studio/help/97906-why-do-i-get-http-basic-access-denied-during-automatic-updates-or-composer-update"
id: "808d567a-de29-410d-8442-a118376f6a78"
---

### HTTP Basic: Access denied 

**Build Stage**

**Job**

**Error Message**

**Category**

**Responsibility**

**Automatic Updates**

Composer Update

`remote: HTTP Basic: Access denied. If a password was provided for Git authentication, the password was incorrect or you're required to use a token instead of a password.`

Application

Customer

**Potential cause**

The most common cause is that the project access token used for Git authentication has expired and needs to be regenerated. All access tokens expire after 12 months.

**Solution**

To resolve this issue, complete the following tasks:

1.  [Generate a new project access token](#generate-new-token).
2.  [Update the corresponding variable in your CI/CD settings](#update-pat-variable).
3.  [Trigger a new pipeline run](#run-automatic-update-pipeline).

#### Generating a new project access token

1.  Log in to the [Code Studio user interface](http://code.acquia.com/).
2.  Navigate to the respective Code Studio project.
3.  In the left sidebar, go to **Settings** > **Access tokens**.
4.  Click **Add new token**.
5.  In the **Token name** field, type `acquia-codestudio`.
6.  In the **Expiration date** field, click the X button to clear the date.
    
    Clearing the date means that the token does not have an expiration.
    
7.  In the **Select a role** field, select **Maintainer**.
8.  In the **Select scopes** section, select the **api** and **write\_repository** checkboxes.
    
    ![acquia-dam\_create-token](https://acquia.widen.net/content/wagb1fisfx/web/fccb1_create%20token.png?w=720&v=523898db-ef93-47b2-9649-ef2f1540099c&itok=jJYLCzho)
    
9.  Click **Create project access token**.
    
    Code Studio generates the token. 
    
10.  Copy the token secret and save it to a secure location as you need to use in the next task.

#### Update the project access token variable

1.  In the left sidebar, go to **Settings** > **CI/CD**.
2.  Expand the **Variables** section.
3.  In the row for `ACQUIA_GLAB_TOKEN_SECRET`, click the pencil icon to edit the variable.
4.  In the **Value** field, add the token secret that you copied earlier.
5.  Click **Save changes**.
    
    ![acquia-dam\_ci-cd-variables](https://acquia.widen.net/content/bwofx17evr/web/cd8fc_edit%20variable.png?w=480&v=636a6c0f-b586-48cf-b480-acb8447a9bf0&itok=aGbCOR3l)
    

#### Running the automatic updates pipeline

1.  In the left sidebar, go to **Build** > **Pipeline schedules**.
2.  In the row for Code Studio Automatic Updates, click the play icon to run the scheduled pipeline.
    
    ![acquia-dam\_pipeline](https://acquia.widen.net/content/77jjo52ypc/web/eedc6_new%20pipeline.png?w=480&v=b1492454-aa48-4827-9400-a8b3eaa61c9e&itok=qOoGVJ6y)
    

Important

If you generate a new token, you must run a new pipeline using the instructions. Clicking the re-run pipeline button on a previous failed pipeline run does not use the new token and continues to fail.