CredentialUnavailableError: ManagedIdentityCredential: Authentication failed. Message uuidFunction is not a function

[brianpham93]

• Package Name: @azure/identity
• Package Version: 3.1.3
• Operating system: Linux
• nodejs
  • version: 12

Describe the bug
Getting error

here's the dependencies from pnpm-lock.yaml

/@azure/identity@3.1.3:
    resolution: {integrity: sha512-y0jFjSfHsVPwXSwi3KaSPtOZtJZqhiqAhWUXfFYBUd/+twUBovZRXspBwLrF5rJe0r5NyvmScpQjL+TYDTQVvw==}
    engines: {node: '>=14.0.0'}
    dependencies:
      '@azure/abort-controller': 1.1.0
      '@azure/core-auth': 1.4.0
      '@azure/core-client': 1.7.2
      '@azure/core-rest-pipeline': 1.10.3
      '@azure/core-tracing': 1.0.1
      '@azure/core-util': 1.3.0
      '@azure/logger': 1.0.4
      '@azure/msal-browser': 2.35.0
      '@azure/msal-common': 9.1.1
      '@azure/msal-node': 1.17.0
      events: 3.3.0
      jws: 4.0.0
      open: 8.4.2
      stoppable: 1.1.0
      tslib: 2.5.0
      uuid: 8.3.2
    transitivePeerDependencies:
      - supports-color
    dev: false

To Reproduce
Steps to reproduce the behavior:

1. Install @azure/identity@3.1.3 in nodejs project running on linux
2. initiate new managed identity const credential = new ManagedIdentityCredential();
3. Get error

CredentialUnavailableError: ManagedIdentityCredential: Authentication failed. Message uuidFunction is not a function
    at ManagedIdentityCredential.getToken (D:\home\site\wwwroot\node_modules\@azure\identity\dist\index.js:2294:23)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)

Expected behavior
Managed identity credential should be initialized successfully

[xirzec]

Looks related to the recent change to remove the uuid dependency:

azure-sdk-for-js/sdk/core/core-util/src/uuidUtils.ts

Line 15 in 2f87259

const uuidFunction =

I think the issue is that you are using Node 12, an unsupported version that has passed out of LTS. The function we're relying on was added in Node 14: https://nodejs.org/dist/latest-v18.x/docs/api/crypto.html#cryptorandomuuidoptions

If you are not able to upgrade to a supported version of Node, I believe you could work around this by depending on the uuid module yourself and assigning it to globalThis.crypto.randomUUID:

import { v4 as uuidv4 } from 'uuid';
globalThis.crypto.randomUUID = uuidv4;

@mpodwysocki does this sound right to you? Maybe we should throw an error here if we can't resolve the expected function that mentions the minimum node version?

[mpodwysocki]

Fixed as of #25555