Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

AFW: SecurityException is possible in BrokerAccountServiceHandler on LG devices #1102

Open
titorodi opened this issue Jan 23, 2018 · 1 comment
Open

AFW: SecurityException is possible in BrokerAccountServiceHandler on LG devices #1102

titorodi opened this issue Jan 23, 2018 · 1 comment
Assignees
@rpdome
Labels
Internal Issue created by a project contributor Issue Triage The engineering team has looked into the issue, understood the issue, labelled/classified the issue More Info Additional information is required to diagnose, troubleshoot, or confirm

Comments

@titorodi
Copy link
Contributor

titorodi commented Jan 23, 2018 •
edited by iambmelt
Loading

Please ensure the following information is provided when logging a new issue:

  • Expected behavior
    • Don't Crash
  • Actual behavior
    • ADAL Crashes on LG devices with the Broker installed on Profile A but the ADAL calling app (e.g. Teams) being in (Work) profile B
  • Steps to reproduce the problem
    • Find an LG device Install the Company Portal in user profile 1 Create a second user profile Install Teams in the second user profile Try to sign in to an AAD account to teams
  • Specifications like the version of the library, operating system etc
  • Relevant logs and traces
    • 01-16 15:42:25.692  5121  6108 E AndroidRuntime: FATAL EXCEPTION: pool-16-thread-1
01-16 15:42:25.692  5121  6108 E AndroidRuntime: Process: com.microsoft.teams, PID: 5121
01-16 15:42:25.692  5121  6108 E AndroidRuntime: java.lang.SecurityException: Uid 1210266 is attempting to illegally masquerade as package com.microsoft.windowsintune.companyportal!
01-16 15:42:25.692  5121  6108 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:1684)
01-16 15:42:25.692  5121  6108 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:1637)
01-16 15:42:25.692  5121  6108 E AndroidRuntime: at com.microsoft.aad.adal.IBrokerAccountService$Stub$Proxy.acquireTokenSilently(IBrokerAccountService.java:151)
01-16 15:42:25.692  5121  6108 E AndroidRuntime: at com.microsoft.aad.adal.BrokerAccountServiceHandler$2.onSuccess(BrokerAccountServiceHandler.java:131)
01-16 15:42:25.692  5121  6108 E AndroidRuntime: at com.microsoft.aad.adal.BrokerAccountServiceHandler$2.onSuccess(BrokerAccountServiceHandler.java:126)
01-16 15:42:25.692  5121  6108 E AndroidRuntime: at com.microsoft.aad.adal.BrokerAccountServiceHandler$5$1.run(BrokerAccountServiceHandler.java:326)
01-16 15:42:25.692  5121  6108 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133)
01-16 15:42:25.692  5121  6108 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607)
01-16 15:42:25.692  5121  6108 E AndroidRuntime: at java.lang.Thread.run(Thread.java:761)
@nazukj nazukj changed the title SecurityException is possible in BrokerAccountServiceHandler on LG devices AFW: SecurityException is possible in BrokerAccountServiceHandler on LG devices Jan 31, 2018
@iambmelt iambmelt assigned iambmelt and unassigned danieldobalian Dec 19, 2019
@iambmelt iambmelt added Internal Issue created by a project contributor Issue Triage The engineering team has looked into the issue, understood the issue, labelled/classified the issue More Info Additional information is required to diagnose, troubleshoot, or confirm labels Dec 19, 2019
@ravarora
Copy link

@iambmelt
Got recent reports of a user facing this.
Device LG Premier Pro running Android 7.1.2
ADAL version used 1.16.3-hf2

@iambmelt iambmelt assigned rpdome and unassigned iambmelt Aug 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rpdome rpdome

Labels
Internal Issue created by a project contributor Issue Triage The engineering team has looked into the issue, understood the issue, labelled/classified the issue More Info Additional information is required to diagnose, troubleshoot, or confirm
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@iambmelt @titorodi @ravarora @danieldobalian @rpdome @nazukj