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
Microsoft authorization within OfficeJS dialog does not redirect to the web page on IOS devices #4397
Comments
Could you please share the add-in manifest so that we can try reproducing the issue on our side? Also, please mention the Outlook version on which you are seeing this issue. |
@anjalitp I am working with Max.
|
@svehera The manifest shared above has localhost URLs, so we can not test using this manifest. Is it possible for you to share manifest with deployed URLs so that we can install and test it? Can you also share which Office JS API you are using for dialog? |
This issue has been automatically marked as stale because it is marked as needing author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. Thank you for your interest in Office Add-ins! |
The user is not able to authorize to the Addin using OfficeJS dialog and Oauth 2.0 authorization code flow https://learn.microsoft.com/en-us/entra/identity-platform/v2-oauth2-auth-code-flow
Previously everything has been working fine. But now it just freezes on the "login.microsoftonline.com" screen and does not redirect to the redirect_uri in the query string.
Besides everything works correctly on Android, Outlook for Windows (Classic and New), Outlook for Mac, and all browsers.
Your Environment
Expected behavior
After successful MS authorization, the user should be redirected to the redirect_uri from the query string.
Current behavior
White screen and no redirect.
Steps to reproduce
Context
It's critical issue because users cannot authorize to the Addin. We use MS authorization as a fallback for SSO (SSO is not supported on mobile).
Video:
movstash.MOV
Screenshot:
The text was updated successfully, but these errors were encountered: