question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

We have trouble to signing in.

See original GitHub issue

Describe the bug Starting from 5 May we observed increasing number of following exceptions while logging from our Android Application on Galaxy Note 10 devices.

AADSTS50194: Application ‘xxx-aaa-vbbb-ccc-xxxx’(XX) is not configured as a multi-tenant application. Usage of the /common endpoint is not supported for such applications created after ‘10/15/2018’. Use a tenant-specific endpoint or configure the application to be multi-tenant.

We are not sure how to reproduce it because it doesn’t happen on all our customers, it just happens on smaller group of users.

Smartphone (please complete the following information):

  • Device: Samsung Galaxy Note 10
  • Android Version: API 30
  • Browser Chrome
  • MSAL Version: 2.0.10

Stacktrace

Caused by com.microsoft.identity.common.exception.ServiceException: AADSTS50194: Application 'XXX'(XXX) is not configured as a multi-tenant application. Usage of the /common endpoint is not supported for such applications created after '10/15/2018'. Use a tenant-specific endpoint or configure the application to be multi-tenant.
Timestamp: 2021-05-14 12:39:43Z
       at com.microsoft.identity.common.internal.result.MsalBrokerResultAdapter.getServiceException(MsalBrokerResultAdapter.java:441)
       at com.microsoft.identity.common.internal.result.MsalBrokerResultAdapter.getBaseExceptionFromExceptionType(MsalBrokerResultAdapter.java:286)
       at com.microsoft.identity.common.internal.result.MsalBrokerResultAdapter.getBaseExceptionFromBundle(MsalBrokerResultAdapter.java:199)
       at com.microsoft.identity.common.internal.result.MsalBrokerResultAdapter.getAcquireTokenResultFromResultBundle(MsalBrokerResultAdapter.java:554)
       at com.microsoft.identity.common.internal.controllers.BrokerMsalController.acquireToken(BrokerMsalController.java:266)
       at com.microsoft.identity.common.internal.commands.InteractiveTokenCommand.execute(InteractiveTokenCommand.java:67)
       at com.microsoft.identity.common.internal.commands.InteractiveTokenCommand.execute(InteractiveTokenCommand.java:39)
       at com.microsoft.identity.common.internal.controllers.CommandDispatcher.executeCommand(CommandDispatcher.java:369)
       at com.microsoft.identity.common.internal.controllers.CommandDispatcher.access$100(CommandDispatcher.java:80)
       at com.microsoft.identity.common.internal.controllers.CommandDispatcher$4.run(CommandDispatcher.java:563)
       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
Caused by com.microsoft.identity.client.exception.MsalServiceException: AADSTS50194: Application 'xxxx'(XXX) is not configured as a multi-tenant application. Usage of the /common endpoint is not supported for such applications created after '10/15/2018'. Use a tenant-specific endpoint or configure the application to be multi-tenant.
Timestamp: 2021-05-14 12:39:43Z
       at com.microsoft.identity.client.internal.controllers.MsalExceptionAdapter.msalExceptionFromBaseException(MsalExceptionAdapter.java:74)
       at com.microsoft.identity.client.SingleAccountPublicClientApplication$3.onError(SingleAccountPublicClientApplication.java:350)
       at com.microsoft.identity.client.SingleAccountPublicClientApplication$3.onError(SingleAccountPublicClientApplication.java:336)
       at com.microsoft.identity.common.internal.controllers.CommandDispatcher.commandCallbackOnError(CommandDispatcher.java:435)
       at com.microsoft.identity.common.internal.controllers.CommandDispatcher.access$1000(CommandDispatcher.java:80)
       at com.microsoft.identity.common.internal.controllers.CommandDispatcher$3.run(CommandDispatcher.java:417)
       at android.os.Handler.handleCallback(Handler.java:938)
       at android.os.Handler.dispatchMessage(Handler.java:99)
       at android.os.Looper.loop(Looper.java:246)
       at android.app.ActivityThread.main(ActivityThread.java:8425)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:596)

To Reproduce Steps to reproduce the behavior:

Not sure how to reproduce that.

Config file:

{
  "client_id": "xxx",
  "authorization_user_agent": "DEFAULT",
  "redirect_uri": "URL",
  "account_mode": "SINGLE",
  "authorities": [
    {
      "type": "AAD",
      "audience": {
        "type": "AzureADMyOrg",
        "tenant_id": "tenand_uuid-xxx-xxx-xxxxxxxx"
      },
      "default": true
    }
  ]
}

Expected behavior User can login to the single tenant app using his account.

Actual Behavior Library return exception because it claims that the user belongs to different tenants that the organization.

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

Additional context Add any other context about the problem here.

Please note: Do not include sensitive information like PII, OII, credentials, secrets, and tokens.

For privacy/security issues please see instructions here

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Reactions:8
  • Comments:16 (6 by maintainers)

github_iconTop GitHub Comments

7reactions
rpdomecommented, May 17, 2021

We’ve identified the issue - this is an issue in our code that got shipped with the latest Authentcator/Company Portal.

The fix currently being rolled out in both apps.

Sorry for any inconvenience this may have caused! -Dome

2reactions
rpdomecommented, May 19, 2021

@GHTaylor, @ryandegruyter We don’t have any other pages for the issue (It’s tracked internally), but I can keep you posted for the rollout status in this thread.

Currently, the fix is being rolled out with Microsoft Authenticator. It’s currently 50% in BETA ring as we speak. We’re aiming to hit 100% prod by 05-22.

Company Portal is planning to go to 100% BETA by tomorrow (05-19).

Read more comments on GitHub >

github_iconTop Results From Across the Web

Sorry, but we're having trouble signing you in - Office 365
Problem. When a user tries to sign in to a Microsoft cloud service such as Microsoft 365, Microsoft Azure, or Microsoft Intune from...
Read more >
Can't sign in to your Google Account
If you can't sign in to your Google Account in Gmail, Google Drive, Google Play, or elsewhere, select the issue that most closely...
Read more >
I can't log in to a website - WhatIsMyBrowser.com
Having trouble logging into a website? There are lots of things that could be wrong. Here's a detailed guide to help you find...
Read more >
How to Fix Windows 10 Login Problems [EXPERT GUIDE]
The first thing you should immediately try is restarting your computer. If you can get to the log in screen, click on the...
Read more >
I'm having trouble signing in through my Android device
I'm having trouble signing in through my Android device · Try turning off your internet connection and switching it back on again. ·...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found