Docker config step missing? 400 reason: connect ECONNREFUSED

I was running the docker version of this twin explorer, and getting a 400 error from the Identity.

per the docs I did:

• Access tokens enabled
• URI callback http://localhost:3000 added

Application runs fine, however the credential issue below.

AuthenticationError: ManagedIdentityCredential authentication failed.(status code 400).
More details:
request to http://169.254.169.254/metadata/identity/oauth2/token?resource=https%3A%2F%2Fdigitaltwins.azure.net&api-version=2018-02-01 failed, reason: connect ECONNREFUSED 169.254.169.254:80
    at ManagedIdentityCredential.<anonymous> (/usr/src/app/client/node_modules/@azure/identity/dist/index.js:1077:23)
    at Generator.throw (<anonymous>)
    at rejected (/usr/src/app/client/node_modules/@azure/identity/node_modules/tslib/tslib.js:112:69)
    at processTicksAndRejections (node:internal/process/task_queues:93:5)

• is it required to add 169.254.169.254 to the callback URI in the app, in addition to localhost?
• is there another place in the system setup where you need to add the DT credentials?

[joseba-altran]

Well, the following Dockerfile does appear to be working fine again. I’ll try to brush it up a little bit (I’ll also try to convert it into a multi-stage build in order to reduce the image size) and create a PR.

FROM node:latest

# Create app directory
WORKDIR /usr/src/app/client

# Install app dependencies
# A wildcard is used to ensure both package.json AND package-lock.json are copied
# where available (npm@5+)
COPY ./client/package*.json ./
WORKDIR /usr/src/app/client/src
RUN npm install
# If you are building your code for production
# RUN npm ci --only=production

# Bundle app source
WORKDIR /usr/src/app
COPY . .

# Install the Azure CLI, which will be required for authentication
RUN curl -sL https://aka.ms/InstallAzureCLIDeb | bash

# Notify that we want to expose port 3000
EXPOSE 3000
# Create startup script & start the app
WORKDIR /usr/src/app/client/src
RUN printf "#!/bin/sh\nset -e\naz login && npm run start" > startup.sh
RUN chmod 0755 startup.sh
ENTRYPOINT ["./startup.sh"]

[joseba-altran]

I can replicate the issue and would say that the problem with the authentication is related to the changes mentioned here: https://github.com/Azure-Samples/digital-twins-explorer/commit/52f6de60a04d32776a626ff05b59ae99656a0154

I have manually tried to install the azure CLI and run az login within the docker image and that seems to work, will have to integrate that into the Dockerfile & update the instructions.