microsoft / microsoft/vscode-azureresourcegroups

[CoR] ENTRA_CLIENT_ID is deployed as a zero-value placeholder causing Tasks API authentication failure

Open
#1,856 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

AT-CTI CoR
Dominant language
TypeScript
Stars
78
Forks
55
Avg merge
16h 49m
Merged PRs (30d)
139

Description

OS: Win11 x64
Build Version: 0.12.8-alpha.0
VS Code Version: Version: 1.137.0

Repro Steps:

  1. Create and deploy a CoR project using the following prompt:
    a to-do list web app with a REST API, PostgreSQL database, Microsoft Entra authentication, and Azure deployment
  2. Complete the workflow and deploy the application to Azure.
  3. Open the deployed application.

Expect:
A valid Microsoft Entra client ID should be configured during deployment so the deployed application can authenticate successfully and access the Tasks API.

Actual:
The application loads, but the Tasks page shows:

Tasks could not be refreshed 
Microsoft Entra configuration is missing
Image

More Info:

  1. The generated Container App is configured with: ENTRA_CLIENT_ID=00000000-0000-0000-0000-000000000000
  2. Backend logs show:
GET /api/tasks
401 Unauthorized
  1. The deployment itself succeeds and the backend health endpoint reports healthy:
GET /api/health
200 OK

However, the application is not functional because requests to the protected Tasks API return 401 Unauthorized.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the deployment configuration that creates the Container App and sets ENTRA_CLIENT_ID; the issue does not name a source file or test. Compare that value with the generated application's authentication configuration, then redeploy and verify that GET /api/tasks no longer returns 401 while GET /api/health remains healthy.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, typescript
Domain
api, authentication, cloud
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.