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
However we get the token response in case of MS Teams and hence the unfurling works there. Looks like this is an outlook specific issue with CloudAdapter usage.
Hi Vignesh-s-s! Thank you for bringing this issue to our attention. We will investigate and if we require further information we will reach out in one business day. Please use this link to escalate if you don't get replies.
Hello @Vignesh-s-s ,
Sorry for the delay in response. We are also experiencing some issues with Cloud Adapter but not exactly able to repro the issue. Will provide you update asap.
@Vignesh-s-s ,
There are some more users who are encountering errors related to token in outlook also we are testing this using multiple samples to confirm if there is any issue related to it in outlook. We will provide you with updates accordingly.
Steps to reproduce
We have been using botframework adapter for our url unfurling scenario, we were able to get the card urfurling work fine in both Teams and Outlook with the SSO token, but after updating to CloudAdapter - https://learn.microsoft.com/en-us/javascript/api/botbuilder/cloudadapter?view=botbuilder-ts-latest
we see that the SSO token is not returned.
While we debugged we found that below code that we use with CloudAdapter, the token response comes as undefined
const tokenResponse = await userTokenClient.getUserToken(
context.activity.from.id,
'OAuthConnectionName',
context.activity.channelId,
magicCodeString
);
Botframework adapter vs Cloud Adapter.docx
Expected behavior
SSO token should be returned in Outlook when unfurling
Actual behavior
SSO token is not returned in Outlook when unfurling
Error details
No response
The text was updated successfully, but these errors were encountered: