InteractiveBrowserCredential has no way to sign out

[jasonjoh]

• Package Name: @azure/identity
• Package Version: 2.0.0-beta.3
• Operating system: Windows
• nodejs
  • version: 14.15.0
• browser
  • name/version: Edge Insiders 92.0.891.1
• typescript
  • version: 4.1.2
• Is the bug related to documentation in
  • README.md
  • source code documentation
  • SDK API docs on https://docs.microsoft.com

Describe the bug
Using the InteractiveBrowserCredential in a React SPA gives no way to sign out once the user is authenticated. I attempted to force a sign out by redirecting the browser to `` which appeared to work, but the next usage of the credential succeeded without any login prompt.

It appears that there are some values left in session storage after the sign out that is causing this.

To Reproduce
Steps to reproduce the behavior:

1. Unzip repro project signout-repro.zip
2. Register a SPA app in the Azure portal with redirect http://localhost:3000
3. Paste your app ID in App.tsx where it says YOUR_APP_ID
4. Run yarn install or npm install
5. Run the app with yarn start or npm start
6. Click Sign in, sign in with an account
7. Click Sign out
8. When returned to the app, click Sign in again.

Expected behavior
You should be prompted to login again inside a pop-up window.

Ideally the credential object should have some function to explicitly invalidate or log out.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

[sadasant]

@jasonjoh Hello Jason, this is Daniel! I’ll be doing my best to help you.

First, I wanted to say that your feedback is noted. We agree that the logout feature is a necessary feature for browser authentication. We are aware of this, and we want to make updates to provide the best Identity story possible for browser users. However, this will take us time, so please bear with us.

In the short term, I’m sorry to say that we’re not planning on implementing a logout method on our credentials. For Node, that shouldn’t be a problem since a new credential can be instantiated, and credentials don’t cache anything that should be meaningful for end-users by default. For browsers, the best we can do in the short term is to provide documentation on creating a custom credential that would use @azure/msal-browser underneath. For that purpose, I’ve created this issue: #15573

We’ll make sure to keep you posted.

[sadasant]

@jasonjoh We have provided the following information in our documentation: https://github.com/Azure/azure-sdk-for-js/blob/main/sdk/identity/identity/samples/AzureIdentityExamples.md#authenticating-with-the-azuremsal-browser-public-client Let me know if that’s helpful!

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!