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

New Outlook authentication does not occur in app #2467

Open
bmedenwald opened this issue Aug 15, 2024 · 3 comments
Open

New Outlook authentication does not occur in app #2467

bmedenwald opened this issue Aug 15, 2024 · 3 comments

Comments

@bmedenwald
Copy link

The Bug in new Outlook (or this library)

When authenticating via this library, a small window within the app appears to collect user information. The below code will popup a window for authentication inside the app for old Teams, new Teams, and old Outlook.

But, the "new" version of Outlook does not work. It pops the user into a web browser, which cannot possibly work as the promise cannot be resolved in a different app.

import { authentication } from "@microsoft/teams-js";

onClick() {
  authentication.authenticate({ height: 625, url: this.localizedUrl(), width: 600 })
    .then(() => {
      alert("success");
    })
    .catch(() => {
      alert("error");
    });
}

Reproduction

To reproduce, simply head to AppSource and install the Simple In/Out application. If you are in any version of Teams or old Outlook, you'll see the popup "in app" correctly. But if you try to log in from new Outlook, you'll see yourself sent to a web browser in error.

I've also reported this here with no helpful workaround or solution.

@bmedenwald bmedenwald changed the title New Outlook p New Outlook authentication does not occur in app Aug 15, 2024
@ChetanSharma-msft
Copy link

Hello @bmedenwald - Thanks for raising your query.
We will look into it and let you know the updates.

@lakhveerk
Copy link
Contributor

Hi Brandon,
The is a known issue and currently being worked on. We will update you with the fix timeline soon.

@krubenok
Copy link

We have checked in a potential fix for this issue and expect it to roll out to production around the end of the Month.

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

4 participants