Closed NewReactUser28 closed 3 years ago
@NewReactUser28 SSO in Teams Tab has different considerations than a normal webpage. Please see this sample for how to SSO in Teams when you don't have a cached account: https://github.com/pnp/teams-dev-samples/tree/master/samples/tab-sso/src/nodejs
@NewReactUser28 could you please let us know if the sample helped resolve your issue? Thanks.
@jasonnutter it would however be very nice if the sso in teams could somehow be integrated in MSAL-angular, but that might be a completely new issue.
NewReactUser28 This issue has been automatically marked as stale because it is marked as requiring author feedback but has not had any activity for 5 days. If your issue has not been resolved please leave a comment to keep this open. It will be closed in 7 days if it remains stale.
Core Library
@azure/msal-browser
Core Library Version
2.13.1
Wrapper Library
@azure/msal-react
Wrapper Library Version
2.13.1
Description
We are trying to extend our SPFx Webparts in Teams tab. this.myMSALObj.getAccountByUsername(this.userName) During MSAL authentication, code is failing when we are trying to obtain the signed in account matching the username. We noticed the account info returned is null.
And we are getting the below error: BrowserAuthError: no_account_error: No account object provided to acquireTokenSilent and no active account has been set. Please call setActiveAccount or provide an account on the request.
Error Message
BrowserAuthError: no_account_error: No account object provided to acquireTokenSilent and no active account has been set. Please call setActiveAccount or provide an account on the request.
Msal Logs
No response
MSAL Configuration
Relevant Code Snippets
Reproduction Steps
Expected Behavior
MSAL authentication must be successful and an access token must be returned.
Identity Provider
Other
Browsers Affected (Select all that apply)
Edge
Regression
NA
Source
Internal (Microsoft)