Teams MSAL2 Provider - no_account_error in "non SSO" mode

[TobiKr]

Hi!

I am trying to acquire an access token with the Teams MSAL2 Provider (instead of creating my own MSAL2 implementation).

async componentDidMount(){
    // Initialize the Microsoft Teams SDK
    microsoftTeams.initialize();

    // Get the user context from Teams and set it in the state
    microsoftTeams.getContext((context: microsoftTeams.Context) => {
      this.setState({context});
    });

    
   // Initialize Graph Toolkit Auth Provider
   TeamsMsal2Provider.microsoftTeamsLib = microsoftTeams;

   let msal2Config: TeamsMsal2Config = {
     clientId: `${process.env.REACT_APP_GRAPH_CLIENTID}`,
     authPopupUrl: '/authpopup',
     scopes: [`${process.env.REACT_APP_GRAPH_SCOPES}`],
     httpMethod: HttpMethod.POST,
     autoConsent: true
     }

   Providers.globalProvider = new TeamsMsal2Provider(msal2Config); 

   let token: string = await Providers.globalProvider.getAccessToken();   
   console.log(token);
   
  }

I am getting this error:

Uncaught (in promise) 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.

What am I missing?

Thanks
Tobias

[sebastienlevert]

Are you using the Toolkit components? The authentication providers are currently meant to be used with the components. For example, this should work when integrating with the Login component as it will do force the authentication flow. This flow is required as Teams doesn't provide a valid access token to call into Microsoft Graph.

[TobiKr]

I am using the people picker and my own components. SSO Flow is working as expected (including the backend service which provides the on behalf flow), but I would like to use auth code flow without a backend service. This works fine if I implement Tab Authentication (https://docs.microsoft.com/en-us/microsoftteams/platform/tabs/how-to/authentication/auth-tab-aad), but it does not work with Teams MSAL2 Provider.

[sebastienlevert]

This definitely sound like something we should be investigating. I created an issue and I'd love if you can use that issue over there to discuss! #1617 I'll be continuing the conversation over there!