You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
blackchoey opened this issue
Dec 1, 2023
· 3 comments
Assignees
Labels
bugSomething isn't workingdotnetChange/fix applies to dotnet. If all three, use the 'JS & dotnet & Python' labelJSChange/fix applies to JS. If all three, use the 'JS & dotnet & Python' label
Please note: any submissions with insufficient reproducible information will be marked as 'Waiting for customer input' and may be closed is there is no response
Describe the bug
If the Teams app manifest does not enable SSO (removing the webApplicationInfo field in the manifest), the OAuth Connection based message extension auth will not work.
Remove webApplicationInfo filed in appPackage/manifest.json
Debug the app
Type profile to show user profile
Message extension shows We didn't find any matches instead of displaying the sign in link
Expected behavior
The Message Extension should provide a link asking user to login.
Screenshots
Desktop(s) (please complete the following information):
OS: [e.g. macOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]
Smartphone (please complete the following information):
Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]
Additional context
The root cause should be our library always use silentAuth for query command, which means using Teams SSO.
One idea to solve this is adding an EnableSSO setting to authentication settings so developer can control whether to use SSO.
The text was updated successfully, but these errors were encountered:
blackchoey
added
dotnet
Change/fix applies to dotnet. If all three, use the 'JS & dotnet & Python' label
JS
Change/fix applies to JS. If all three, use the 'JS & dotnet & Python' label
labels
Dec 1, 2023
blackchoey
changed the title
[Bug]: OAuth Connection based message extension auth does not work if not enable SSO
[Bug]: [JS & dotnet] OAuth Connection based message extension auth does not work if not enable SSO
Dec 1, 2023
@blackchoey The webApplicationInfo property is required for non-SSO scenarios as well. To enable SSO in OAuth connection is to set the token exchange url property. And to disable it, is to set it blank.
@singhk97 I tried to set the resource property under webApplicationInfo to empty, as well as removed token exchange url from the OAuth Connection on Azure Bot Service, but still observed the same problem.
#1236)
## Linked issues
closes: #1194#991
## Details
* Corresponding JS PR: #1232 for implementation details.
## Attestation Checklist
- [x] My code follows the style guidelines of this project
- I have checked for/fixed spelling, linting, and other errors
- I have commented my code for clarity
- I have made corresponding changes to the documentation (updating the
doc strings in the code is sufficient)
- My changes generate no new warnings
- I have added tests that validates my changes, and provides sufficient
test coverage. I have tested with:
- Local testing
- E2E testing in Teams
- New and existing unit tests pass locally with my changes
---------
Co-authored-by: Corina <[email protected]>
bugSomething isn't workingdotnetChange/fix applies to dotnet. If all three, use the 'JS & dotnet & Python' labelJSChange/fix applies to JS. If all three, use the 'JS & dotnet & Python' label
Please note: any submissions with insufficient reproducible information will be marked as 'Waiting for customer input' and may be closed is there is no response
Describe the bug
If the Teams app manifest does not enable SSO (removing the
webApplicationInfo
field in the manifest), the OAuth Connection based message extension auth will not work.To Reproduce
webApplicationInfo
filed inappPackage/manifest.json
profile
to show user profileWe didn't find any matches
instead of displaying the sign in linkExpected behavior
The Message Extension should provide a link asking user to login.
Screenshots
Desktop(s) (please complete the following information):
Smartphone (please complete the following information):
Additional context
The root cause should be our library always use
silentAuth
for query command, which means using Teams SSO.One idea to solve this is adding an
EnableSSO
setting to authentication settings so developer can control whether to use SSO.The text was updated successfully, but these errors were encountered: