@azure/identity: app never exits when using InteractiveBrowserCredential

[sinedied]

• Package Name: @azure/identity
• Package Version: 2.0.4
• Operating system: MacOS 12.3.1
• nodejs
  • version: 16.14.0
• browser
  • name/version:
• typescript
  • version:
• Is the bug related to documentation in
  • README.md
  • source code documentation
  • SDK API docs on https://docs.microsoft.com

Describe the bug
When authenticating using InteractiveBrowserCredential on MacOS and not using cached credentials, the app never exits. I suspect that the local server used to catch the auth callback is never closed. Using any other auth methods works without having the app stuck at the end.

From some testing with my colleagues, the problem seems to only occur on MacOS, though I did not get the chance to try it myself on Windows and Linux.

To Reproduce
Steps to reproduce the behavior:

1. Try to authenticate in a Node.js app with

  const browserCredential = new InteractiveBrowserCredential({
    redirectUri: `http://localhost:31337`,
    tenantId: "<your tenant>,
  });
  await browserCredential.getToken("profile")
  console.log("login success");

2. After login is successful, app never exits.

Expected behavior
The app exists properly after an interactive browser login.

[KarishmaGhiya]

@sinedied Thank you for reporting. We were able to reproduce this issue on mac, but works fine on windows. We are investigating into this.

[KarishmaGhiya]

@sinedied We did some investigation on our end and found that this issue exists on both Mac and linux OS. We do have a workaround for Mac OS but this workaround still doesn't work for linux. We have filed an issue on the open dependency - sindresorhus/open#287

For now we will release the bug fix 2.0.5 so that we can unblock your issue. We will let you know when we release.
cc: @mpodwysocki

[KarishmaGhiya]

@sinedied We have released the @azure/identity 2.0.5 which solves the issue on Mac OS. Please let us know if that works for you and if you have any questions.

[ghost]

Hi, we're sending this friendly reminder because we haven't heard back from you in a while. We need more information about this issue to help address it. Please be sure to give us your input within the next 7 days. If we don't hear back from you within 14 days of this comment the issue will be automatically closed. Thank you!

[sinedied]

Sorry for the lag @KarishmaGhiya, I just tested 2.0.5 and it perfectly fixes the issue, thanks! 👍