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.

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

Teamjs returning incorrect UPN for guest users in a AAD tenant #2466

Open
ashishsaini11 opened this issue Aug 15, 2024 · 8 comments
Open

Teamjs returning incorrect UPN for guest users in a AAD tenant #2466

ashishsaini11 opened this issue Aug 15, 2024 · 8 comments

Comments

@ashishsaini11
Copy link

For guest users in a tenant, the UPN returned by Teams JS is not correct. It returns the guest user's email address instead of the actual UPN, which includes #EXT. This discrepancy causes issues with identifying users.
Actual UPN:
image

Returned by teamsjs
image

@lakhveerk
Copy link
Contributor

Hi Ashish!
Thank you for reporting the issue. Can you answer some questions to help investigate the issue please:

  1. What API you were using to get the UPN info?
  2. I assume this happened in Teams host. What Teams version are you using?
  3. Is this something new that you have started noticing or was that always returning email instead of UPN?

@priytosh-tripathi
Copy link

priytosh-tripathi commented Aug 16, 2024

Hi lakhveerk,

Here is what we found,

  1. We're using authenticaion.getuser.
  2. We've got the result from Host Names - Teams and TeamsModern. Our customers are facing issues on both of these Hosts.
  3. We've started noticing this issues 2 months back, but we're not sure when it all started. Upon investigation we found this issue.

@ChetanSharma-msft
Copy link

Hello @priytosh-tripathi - Could you please share the teamsJS and other Teams client related versions?

@ashishsaini11
Copy link
Author

@ChetanSharma-msft we are using 2.22.0 of teams-js.

@Meghana-MSFT
Copy link

@ashishsaini11 - We are able to repro this. We raised a bug for this, we will keep you posted on the updates. Thank you.

@ashishsaini11
Copy link
Author

Thanks @Meghana-MSFT . Could you please share the workitem which we can track.

@Meghana-MSFT
Copy link

@ashishsaini11 - Unfortunately the bug is internal to Microsoft, and we cannot share it outside.

@Meghana-MSFT
Copy link

@ashishsaini11 - This bug has been fixed, we have verified the fix at our end. Could you also please check once at your end.

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants