microsoft-authentication-library-for-android icon indicating copy to clipboard operation
microsoft-authentication-library-for-android copied to clipboard

Device identifier: Not available during ISingleAccountPublicClientApplication signIn

Open rajohns08 opened this issue 1 year ago • 0 comments

Describe the bug My app is live and in production. I see the below screenshot after signing in using the ISingleAccountPublicClientApplication signIn method. My device is already registered in Intune despite the message saying otherwise. The Azure backend dev on my team confirmed our conditional access policy is failing because they don't receive a device ID.

Smartphone (please complete the following information):

  • Device: This happens on every device I've tried but the most recent device is a Samsung Galaxy A20
  • Android Version: 11, 12, 14
  • Browser: This is an in-app webview per my msal configuration
  • MSAL Version: 4.0.5

To Reproduce Steps to reproduce the behavior: Simply call the ISingleAccountPublicClientApplication signIn method.

If related to development, please provide relevant configuration details necessary to understand your problem including any relevant traces, logs, or otherwise.

Config file:

{
  "client_id" : "<redacted>",
  "authorization_user_agent" : "WEBVIEW",
  "redirect_uri" : "<redacted>",
  "broker_redirect_uri_registered" : true,
  "authorities" : [
    {
      "authority_url": "<redacted>",
      "type": "B2C",
      "audience": {
        "tenant_id": "myidaasuat.onmicrosoft.com",
        "type": "AzureADandPersonalMicrosoftAccount"
      }
    }
  ],
  "account_mode": "SINGLE"
}

Expected behavior Device ID is passed to backend, and I don't see this message telling me my device isn't registered. Signin works.

Actual Behavior Device ID isn't passed to backend, and I see this message saying my device isn't registered.

Screenshots msal2

Additional context I enabled MSAL logging and got the below log file: logs.txt

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

For privacy/security issues please see instructions here

rajohns08 avatar Jul 03 '24 15:07 rajohns08