OfficeDev / OfficeDev/Office-Addin-TaskPane-SSO-JS
SSO Fails for Teams Desktop App
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 12
- Forks
- 21
- Avg merge
- 6h 9m
- Merged PRs (30d)
- 1
Description
Prerequisites
Please answer the following questions before submitting an issue.
YOU MAY DELETE THE PREREQUISITES SECTION.
- I am running the latest version of Node and the tools
- I checked the documentation and found no answer
- I checked to make sure that this issue has not already been filed
Expected behavior
Please describe the behavior you were expecting
SSO Add-Ins should work on teams desktop app as well.
Current behavior
Not able to generate access token using getAccessToken() method in teams desktop app, it shows the a pop where add in asks to open other pop up screen but once allowed it shows a blank pop up for fraction of seconds and then nothing happens.
Steps to Reproduce
Please provide detailed steps for reproducing the issue.
- create a sso project using yo office with javascript..
- configure the sso, and deploy it to azure web app and manifest to admin center
- open desktop app try to click 'get user profile information' but which tries to get access token and fails.
- you get it...
Context
Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.
- Operating System:windows
- Node version:16.6
- Office version:1.9.7
- Tool version:
Failure Logs
Please include any relevant log snippets, screenshots or code samples here.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the JavaScript SSO project created using yo office and reproduce the failure in the Teams desktop app after deploying to an Azure web app and configuring the manifest. Trace the getAccessToken() call triggered by “get user profile information” and compare the desktop flow with the expected token flow. Done means the access token is generated and the profile action works in the desktop app.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, javascript, node.js
- Domain
- authentication, desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100