authentication.getAuthToken throwing generic vague error messages

[alexchaaan]

Hi Team,

We were hoping to get more clarity around some of the error messages we're seeing with some authentication.getAuthToken() calls. This is causing our app to have an infinite loader as we're always expecting the jwt token to exist. This call works almost all of the time but we're seeing some errors with some users. Here's a list of some different errors we're seeing:

• Error: Error

• Error: Get Auth token failed

• Error: Error: Invalid authResponse received from msal for resource::api:redacted

• Error: Get Auth token failed

• Error: Error: Unexpected {"Description":"(pii)","Domain":"com.microsoft.oneauth","ErrorCode":"1001","Message":"An unexpected error occurred.","SystemErrorCode":"1067","Tag":"5fcl8","Type":"OneAuth","additional_query_parameters_count":"1","all_error_tags":"5fcl8","api_error_code":"1067","api_error_context":"(pii)","api_error_tag":"5fcl8","api_name":"AcquireTokenInteractively","api_status_code":"StatusInternal::Unexpected","auth_flow":"Broker","authority_type":"AAD","authorization_type":"Interactive","broker_app_used":"true","client_id":"redacted","correlation_id":"redacted","is_successful":"false","msal_version":"1.1.0+00747db6","original_authority":"https://login.microsoftonline.com/redacted","request_duration":"1584","request_eligible_for_broker":"true","start_time":"2024-03-27T20:36:45.000Z","stop_time":"2024-03-27T20:36:47.000Z","ui_event_count":"1","was_request_throttled":"false"}

• Error: Error: Unexpected {"Description":"(pii)","Domain":"com.microsoft.oneauth","ErrorCode":"1001","Message":"An unexpected error occurred.","SystemErrorCode":"3400073241","Tag":"5fcl9","Type":"OneAuth","additional_query_parameters_count":"1","all_error_tags":"5fcl9","api_error_code":"3400073241","api_error_context":"(pii)","api_error_tag":"5fcl9","api_name":"AcquireTokenInteractively","api_status_code":"StatusInternal::Unexpected","auth_flow":"Broker","authority_type":"AAD","authorization_type":"Interactive","broker_app_used":"true","client_id":"redacted","correlation_id":"redacted","is_successful":"false","msal_version":"1.1.0+00747db6","original_authority":"https://login.microsoftonline.com/redacted","request_duration":"75887","request_eligible_for_broker":"true","start_time":"2024-03-28T14:21:48.000Z","stop_time":"2024-03-28T14:23:04.000Z","ui_event_count":"1","wam_telemetry":"{\"ui_visible\":true,\"scope\":\"api://redacted/.default offline_access openid profile","redirect_uri":"ms-appx-web://…

• Error: CancelledByUser

• Error: Error: ApiContractViolation {"Description":"Embedded browser flow resulted in 'invalid_client' with description '(pii)'","Domain":"com.microsoft.oneauth","ErrorCode":"2400","Message":"The operation attempted is invalid.",

[jekloudaMSFT]

Hi @alexchaaan, thanks for raising this. Can I know what platform you're seeing these issues on? Is this specific to Teams Classic or Teams Modern?

[Vaibhav-MSFT]

Hi @alexchaaan ,
Can you please let us know if you are trying to run any Microsoft Teams App development samples and can you provide us with some repro steps?

[alexchaaan]

@jekloudaMSFT this is from our logs from some customers, not sure if it's classic or modern but I imagine mostly modern

@Vaibhav-MSFT unfortunately this is from our app in prod. here's the code that's logging the errors:

export function getTeamsJwt(): Promise<string> {
	return authentication.getAuthToken();
}

	useEffect(() => {
		const loadToken = async () => {
			try {
				const jwtToken = await getTeamsJwt();
				setJwtToken(jwtToken);
			} catch (err) {
				setIsLoading(false);
				throw err;
			}
		};
		loadToken().catch(error => {
			datadogLogs.logger.error('Error in TeamsAuthWrapper loadToken', {}, error);
			calmLogger.error('Error in TeamsAuthWrapper loadToken', {}, error);
		});
	}, []);

and this is a component thats rendered after the sdk is initialized

[Vaibhav-MSFT]

Hello @alexchaaan ,
Check that the client credentials (such as client ID, client secret, or certificate) used to authenticate your app are correct. Ensure that the credentials are properly configured in your app registration in Azure Active Directory (Azure AD).
Also Verify that your app registration in Azure AD has the necessary permissions.

[alexchaaan]

@Vaibhav-MSFT this works for most users. it for sure works on our own tenant. if the credentials and app registration were wrong, wouldn't it fail every time?

[alexchaaan]

bump
what could be the causes of that function failing sometimes?

[Vaibhav-MSFT]

We are checking your query with engineering team and let you know once we get any updates from them. Thanks.