Closed dmcweeney closed 1 year ago
@theentropic, @christophepeerens - Could you please share your Email id's so that I can setup a call accordingly. Till then, could you please try with the Microsoft Teams Desktop client for the issue.
@niteshjain1987 - I looked at the manifest, I don't see any issue specific to SSO. Can't test the manifest as there are no Ids mentioned. I'll try and repro it with demo app and share the results.
Btw, Manifest only supports RSC permissions, so highlighted ones can be removed. (This is not related to issue with SSO you are facing).
@Wajeed-msft As per your suggestion issue has been resolved for me. Thanks.
@theentropic, @christophepeerens - Is your issue resolved or still looking for any help? If yes, Could you please share your Email id's so that I can setup a call accordingly.
If your issue already resolved, could you please it.
@v-chetsh Sorry, I was away on holiday for the past few days. It appears the issue still persists for me on both desktop and web app versions of teams. You can reach out to me by email via evan (dot) abramson (at) cireson (dot) com.
@theentropic - Please let us know your best suitable time so that I can setup a call accordingly.
I'm available the rest of the week between 9:30 am est and 3pm est
@theentropic @v-chetsh
I'm also facing the same issue. I have gone through all the comments. There is no solution proposed in the comments. Does this issue got resolved? If it is resolved what is the solution for it?
Thanks, Abhiram.
@Abhiram219 - Can you please try below suggestion by @christophepeerens
I haven't had a problem for two weeks. The only change I made is to call the "microsoftTeams.getContext()" only at startup. Previously, I called "microsoftTeams.getContext()" in other functions (and the one that calls "microsoftTeams.authentication.authenticate()"). No idea if this avoids the problem or not. But I would like to be sure that this completely solves the problem ;-)
@theentropic Could you please confirm if your issue has resolved? If yes, can you share the steps you have followed.
The way I was able to resolve my problem was by assigning the custom domain to my tenant when creating the api:// link. Once that custom domain was validated, the SSO token started working.
@Abhiram219 - Can you please confirm by doing what @theentropic suggested?
@Abhiram219 - Could you please confirm if your issue has resolved with above suggestion or still looking for any help?
@sayali-MSFT - We are using a multi-tenant setup and it's working for all clients except for one client. We cannot add a custom domain for this use case (theentropic- proposed solution).
And coming to christophepeerens suggestion - we are doing below to get authToken
microsoftTeams.authentication.getAuthToken(authTokenRequest); and we are calling microsoftTeams.getContext() once we have the valid token.
We are still facing this issue.
Did you tried directly consenting all the permissions by Admin from App registration page?
Thanks
@HunaidHanfee-MSFT
Admin Consent is granted from App registration page. We are still seeing this issue.
Can you please share the error from console, you are getting?
Thanks
@Abhiram219 - Did you get a chance to check for error?
@HunaidHanfee-MSFT One of our customers is facing this issue. We posted to them for the console error. Once we get an update from them I will post it here.
But I can guarantee that the error in the console is the same as the error in this comment. Previously we got on to a call and found that these are the same error logs in the console.
@Abhiram219 - Can you confirm that if this issue is persistent or getting it sometime? It would be better if you provide environment where we can have the repro and debug it our side?
Thanks
@HunaidHanfee-MSFT The issue is intermittent and we are observing this issue with only one specific customer. For the rest of our customers, it's working fine. We are unable to reproduce this issue at our end. Will ask the customer to provide the environment.
Thanks.
@Abhiram219 - Any updates on this issue?
@HunaidHanfee-MSFT The issue is the same as the issue in this comment and the issue is intermittent.
Could you please help us get a repro? We are unable to debug it.
Currently, we are also unable to reproduce at our end. We will ask the customer for an instance where it can be reproducible. We will get back once we got an update from the customer.
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 3 days. It will be closed if no further activity occurs within 3 days of this comment.
Hi Team I have integrated service now with teams wherein service now custom portal page is open with in team web as well as desktop client. Many a times it opens the page smoothly and other day ot see the token renewal time out. It does not gets solved for at least few hours and then it will work fine for few hrs .i have followed all the suggestion given here still no luck.i have ticket open with Microsoft and service now and yet to get solution.
Hello @ssinghaniacoforge, we are unable to repro it at our side, if you could share test environment where you are seeing this issue happening then we can do debugging and try looking for what's wron. @Abhiram219 - Any updates?
Thanks
@HunaidHanfee-MSFT, @ssinghaniacoforge is the person who is facing the issue. They can provide an environment where you can debug.
@ssinghaniacoforge Can you please provide an environment to debug.
Hi Team Pl send out an meeting invite today or tomorrow bet 6 pm ist yo 7 pm ist where I can walk you through the environment and the issue..if lucky, you will be able see issue Thanks Shashi
Get Outlook for Androidhttps://aka.ms/AAb9ysg
From: Abhiram219 @.> Sent: Tuesday, December 28, 2021 2:37:42 PM To: OfficeDev/microsoft-teams-library-js @.> Cc: Shashikant Navalkishor Singhania @.>; Mention @.> Subject: Re: [OfficeDev/microsoft-teams-library-js] renewalTimeout from getAuthToken (#532)
CAUTION: This email originated from outside the organization. Do not click on links or open any attachment unless you recognize the source of this email, trust the sender and know the content is safe.
@HunaidHanfee-MSFThttps://ind01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FHunaidHanfee-MSFT&data=04%7C01%7Cshashikant.2.s%40coforge.com%7Cd481409015aa43d0de5b08d9c9e182ee%7Cb727a530a0d54fb8bd40d8f9763e97db%7C0%7C0%7C637762792679968996%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=9I35E8nUMMwyDkkespAj6LLh2OmpygaMfv2Ey2LRCvY%3D&reserved=0, @ssinghaniacoforgehttps://ind01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fssinghaniacoforge&data=04%7C01%7Cshashikant.2.s%40coforge.com%7Cd481409015aa43d0de5b08d9c9e182ee%7Cb727a530a0d54fb8bd40d8f9763e97db%7C0%7C0%7C637762792679978954%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=dMGX556mFUqQDoFJ9BkLp2az7VHOxPlDXenfkSt6jbg%3D&reserved=0 is the person who is facing the issue. They can provide an environment where you can debug.
@ssinghaniacoforgehttps://ind01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fssinghaniacoforge&data=04%7C01%7Cshashikant.2.s%40coforge.com%7Cd481409015aa43d0de5b08d9c9e182ee%7Cb727a530a0d54fb8bd40d8f9763e97db%7C0%7C0%7C637762792679988911%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=Jt7K7Lz3pLr%2BEGyVruSwqXtR%2BqTqirRyMcYDllDVDrg%3D&reserved=0 Can you please provide an environment to debug.
— Reply to this email directly, view it on GitHubhttps://ind01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FOfficeDev%2Fmicrosoft-teams-library-js%2Fissues%2F532%23issuecomment-1001952683&data=04%7C01%7Cshashikant.2.s%40coforge.com%7Cd481409015aa43d0de5b08d9c9e182ee%7Cb727a530a0d54fb8bd40d8f9763e97db%7C0%7C0%7C637762792679988911%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=bkrH7vxktkQ4tZo4J8SN%2B8lA%2BphxOevqWOl1j%2B%2BThV8%3D&reserved=0, or unsubscribehttps://ind01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAXBXZSQE4XCSYWLLS43ARGLUTF455ANCNFSM4ZTJIIMA&data=04%7C01%7Cshashikant.2.s%40coforge.com%7Cd481409015aa43d0de5b08d9c9e182ee%7Cb727a530a0d54fb8bd40d8f9763e97db%7C0%7C0%7C637762792679998863%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=RPsLMlqSvB3H23fjm%2FYv5lochSoZ3iDl8EUmxEL2Zoo%3D&reserved=0. Triage notifications on the go with GitHub Mobile for iOShttps://ind01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04%7C01%7Cshashikant.2.s%40coforge.com%7Cd481409015aa43d0de5b08d9c9e182ee%7Cb727a530a0d54fb8bd40d8f9763e97db%7C0%7C0%7C637762792679998863%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=4HbljYJEL2Xg9EWeMzFQGLxeKpnE8bcgDEaWq1IRcVY%3D&reserved=0 or Androidhttps://ind01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04%7C01%7Cshashikant.2.s%40coforge.com%7Cd481409015aa43d0de5b08d9c9e182ee%7Cb727a530a0d54fb8bd40d8f9763e97db%7C0%7C0%7C637762792680008832%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=SISYBvnViuTPhHwKQ7dnnkm%2B77gn1EzWuwTy9LNdgpY%3D&reserved=0. You are receiving this because you were mentioned.Message ID: @.***>
DISCLAIMER: The information transmitted, including any attachments, is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you receive this email by mistake, please advise the sender and delete it immediately. Email transmission cannot be guaranteed to be secure, or error free as information could be intercepted, corrupted, lost or destroyed as a result of the transmission process. Views or opinions presented in this email are solely those of the author and do not necessarily represent those of the Company. Through this e-mail, no employee or agent is authorized to conclude/commit any new or incidental terms, which are not part of the original contract with the client or vendor, other than by way of duly executed and signed amendment contract between the parties in accordance with the agreed protocol of the contract. Please be aware that the Company monitors e-mail communications through our networks for regulatory compliance purposes. Coforge Limited and its related entities consider the privacy of its clients to be of utmost importance and works to protect it. The Privacy Policy of the Company can be accessed from our website www.coforge.com.
Sure, We can connect. Can you share alias so that I can schedule meeting today 6:30-7:00 PM IST?
Yes Please
From: Hunaid Hanfee-MSFT @.> Sent: 30 December 2021 16:36 To: OfficeDev/microsoft-teams-library-js @.> Cc: Shashikant Navalkishor Singhania @.>; Mention @.> Subject: Re: [OfficeDev/microsoft-teams-library-js] renewalTimeout from getAuthToken (#532)
CAUTION: This email originated from outside the organization. Do not click on links or open any attachment unless you recognize the source of this email, trust the sender and know the content is safe.
Sure, We can connect. Can you share alias so that I can schedule meeting today 6:30-7:00 PM IST?
- Reply to this email directly, view it on GitHubhttps://ind01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FOfficeDev%2Fmicrosoft-teams-library-js%2Fissues%2F532%23issuecomment-1002980542&data=04%7C01%7Cshashikant.2.s%40coforge.com%7C442f642e43de410e5a4c08d9cb844e41%7Cb727a530a0d54fb8bd40d8f9763e97db%7C0%7C0%7C637764591379169894%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=6yVWMas3Fi3kWYAAiJwSxvy9BPwk%2FntjrFBP80nKli4%3D&reserved=0, or unsubscribehttps://ind01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAXBXZSWSFTHSBHTP7VSCE33UTQ4H3ANCNFSM4ZTJIIMA&data=04%7C01%7Cshashikant.2.s%40coforge.com%7C442f642e43de410e5a4c08d9cb844e41%7Cb727a530a0d54fb8bd40d8f9763e97db%7C0%7C0%7C637764591379169894%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=LzKjM%2BsMGZPwdi0IAtSkXdfa17Ei9O%2Ffz73GCaWhiec%3D&reserved=0. Triage notifications on the go with GitHub Mobile for iOShttps://ind01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04%7C01%7Cshashikant.2.s%40coforge.com%7C442f642e43de410e5a4c08d9cb844e41%7Cb727a530a0d54fb8bd40d8f9763e97db%7C0%7C0%7C637764591379169894%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=QWeImBzVA9Mj6Og3CQDTa0NkrfDMlSqYYQs1jV8gLHg%3D&reserved=0 or Androidhttps://ind01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04%7C01%7Cshashikant.2.s%40coforge.com%7C442f642e43de410e5a4c08d9cb844e41%7Cb727a530a0d54fb8bd40d8f9763e97db%7C0%7C0%7C637764591379169894%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=oyZQBG10luzVizfwO9XoGmLT1tUUE35FpC748TH8thg%3D&reserved=0. You are receiving this because you were mentioned.Message ID: @.**@.>>
DISCLAIMER: The information transmitted, including any attachments, is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you receive this email by mistake, please advise the sender and delete it immediately. Email transmission cannot be guaranteed to be secure, or error free as information could be intercepted, corrupted, lost or destroyed as a result of the transmission process. Views or opinions presented in this email are solely those of the author and do not necessarily represent those of the Company. Through this e-mail, no employee or agent is authorized to conclude/commit any new or incidental terms, which are not part of the original contract with the client or vendor, other than by way of duly executed and signed amendment contract between the parties in accordance with the agreed protocol of the contract. Please be aware that the Company monitors e-mail communications through our networks for regulatory compliance purposes. Coforge Limited and its related entities consider the privacy of its clients to be of utmost importance and works to protect it. The Privacy Policy of the Company can be accessed from our website www.coforge.com.
Could you please send us a mail mention here https://docs.microsoft.com/en-us/microsoftteams/platform/feedback#product-support-channels in general question section?
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 3 days. It will be closed if no further activity occurs within 3 days of this comment.
@ssinghaniacoforge - Gentle reminder
Could you please send us a mail mention here https://docs.microsoft.com/en-us/microsoftteams/platform/feedback#product-support-channels in general question section?
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 3 days. It will be closed if no further activity occurs within 3 days of this comment.
Hi Hanfee, I am seeing the issue as of now. I am attaching HAR logs and console log for your reference. Thanks Shashi
From: Hunaid Hanfee-MSFT @.> Sent: 27 December 2021 18:15 To: OfficeDev/microsoft-teams-library-js @.> Cc: Shashikant Navalkishor Singhania @.>; Mention @.> Subject: Re: [OfficeDev/microsoft-teams-library-js] renewalTimeout from getAuthToken (#532)
CAUTION: This email originated from outside the organization. Do not click on links or open any attachment unless you recognize the source of this email, trust the sender and know the content is safe.
Hello @ssinghaniacoforgehttps://ind01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fssinghaniacoforge&data=04%7C01%7Cshashikant.2.s%40coforge.com%7Cd3b4b9e82cb743194f7308d9c937e9e5%7Cb727a530a0d54fb8bd40d8f9763e97db%7C0%7C0%7C637762065918238604%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=9CWwawCsxwM5jiVIDPRUaIYy4OVw4w8mClTIhGahCiI%3D&reserved=0, we are unable to repro it at our side, if you could share test environment where you are seeing this issue happening then we can do debugging and try looking for what's wron. @Abhiram219https://ind01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAbhiram219&data=04%7C01%7Cshashikant.2.s%40coforge.com%7Cd3b4b9e82cb743194f7308d9c937e9e5%7Cb727a530a0d54fb8bd40d8f9763e97db%7C0%7C0%7C637762065918238604%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=N7FaAkU%2BhfRynWlsVL0wzjCFcUSxUikkzjAbE6RaacU%3D&reserved=0 - Any updates?
Thanks
- Reply to this email directly, view it on GitHubhttps://ind01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FOfficeDev%2Fmicrosoft-teams-library-js%2Fissues%2F532%23issuecomment-1001552263&data=04%7C01%7Cshashikant.2.s%40coforge.com%7Cd3b4b9e82cb743194f7308d9c937e9e5%7Cb727a530a0d54fb8bd40d8f9763e97db%7C0%7C0%7C637762065918238604%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=0hVd9gzTpLhddJxsaSHPjwfrL%2FVWDEK5NXaSZjJb5rE%3D&reserved=0, or unsubscribehttps://ind01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAXBXZSVD7YWRBJFMLK4ILZLUTBNTXANCNFSM4ZTJIIMA&data=04%7C01%7Cshashikant.2.s%40coforge.com%7Cd3b4b9e82cb743194f7308d9c937e9e5%7Cb727a530a0d54fb8bd40d8f9763e97db%7C0%7C0%7C637762065918238604%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=EQDnN%2BAULUp0xergjVzpjd24d3ypsQs1fZPjqoCtK6c%3D&reserved=0. Triage notifications on the go with GitHub Mobile for iOShttps://ind01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04%7C01%7Cshashikant.2.s%40coforge.com%7Cd3b4b9e82cb743194f7308d9c937e9e5%7Cb727a530a0d54fb8bd40d8f9763e97db%7C0%7C0%7C637762065918238604%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=PN6eWMXSF9DMPlUB4EAtlMbSIXQvc8RTZbOM%2FpasFn8%3D&reserved=0 or Androidhttps://ind01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04%7C01%7Cshashikant.2.s%40coforge.com%7Cd3b4b9e82cb743194f7308d9c937e9e5%7Cb727a530a0d54fb8bd40d8f9763e97db%7C0%7C0%7C637762065918238604%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=iKK5CMESHPLHRCVESj%2Bj4mVkbSM2MdyWOSaBKq6M%2B0c%3D&reserved=0. You are receiving this because you were mentioned.Message ID: @.**@.>>
DISCLAIMER: The information transmitted, including any attachments, is intended only for the person or entity to which it is addressed and contains confidential and/or privileged material. Sharing this message or its contents with a third party without prior written consent is strictly prohibited. If you receive this email by mistake, please advise the sender and delete it immediately. Email transmission cannot be guaranteed to be secure or virus-free as information could be intercepted, corrupted, lost or destroyed as a result of the transmission process. Therefore, you should check the email for threats with proper software, as the Company does not accept liability for any damage inflicted by viewing the content of this email. Views or opinions presented in this email are solely those of the author and do not necessarily represent those of the Company. Through this email, no employee or agent is authorized to conclude/commit any new or incidental terms, which are not part of the original contract with any client or vendor, other than by way of duly executed and signed amendment contract between the parties in accordance with the agreed protocol of the contract. Coforge Limited and its related entities consider the privacy of its clients to be of utmost importance and work to protect it. Please be aware that the Company monitors email communications through our networks for compliance purposes. The Privacy Policy of the Company can be accessed from our website www.coforge.com.
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 3 days. It will be closed if no further activity occurs within 3 days of this comment.
Hello @ssinghaniacoforge, Could you please share the logs either directly on GitHub or send us a mail mention here microsoftteamsdev@microsoft.com ?
@ssinghaniacoforge - Thanks for sharing the logs, I have created a bug and attached the logs you shared. Internal engineering team will try to have a repro at their end. We can't share an ETA but I will let you know the updates.
Hey @HunaidHanfee-MSFT - we are running a Teams App Hack here in the UK, and one of our partners is also seeing this issue. I've worked with 50+ Partners over the last 2 years, and never seen the getAuthToken function fail with renewalTimeout. In my experience, this SSO method has always been pretty bulletproof. The only weirdness I can see with this specific partner app, is that they have a task module, that is invoked from a bot adaptive card, that is hosted on a different domain, to the web-app, which is then being iFramed inside the task module. I've asked them to merge the 2 projects, so that the bot and the web-app are all hosted and accessible through the same NGROK domain. I will report back if this fixes the issue. Thanks!
Any update on this? We are seeing another partner with this issue at a hands-on lab event here in the UK.
@jalew123 - Could you please let us know if your customer faces this issue intermittently or do they have consistent repro?
Hey @Meghana-MSFT - it's really random, although when this error occurs, it seems to stick around for that specific app, for a long period of time. We ran a Teams Apps hands-on lab on Monday, and out of the 15 attendees, who were all working on the same code (from here https://github.com/OfficeDev/msteams-sample-contoso-hr-talent-app ), and only 1 attendee had this issue, and we couldn't get it fixed during the lab. As it's the SSO service (that we operate that does the on-behalf-of behind the scenes) that is returning this 'renewalTimeout' error response, when getAuthToken() is called, there must be some way of seeing what causes this, if we can find the right person in Engineering who can troubleshoot this for us. I'm happy to jump on a Teams meeting if you'd like to discuss this further. Please let me know, my alias in Microsoft is jalew if you want to start a Teams chat off too. Cheers!
@dmcweeney - Could you please share Teams Client Logs from users hitting this issue? The auth stack logs a lot more details regarding the errors coming back from the auth library. Please follow this doc to get client logs - https://docs.microsoft.com/en-us/microsoftteams/log-files#debug-logs
@Meghana-MSFT we have not had this problem in a long time! If we hit it again I will be sure to share the logs.
I don't know if it is related to this, but I just had a breakthrough in dealing with what I think is a similar issue with Teams. I was getting caa70004
errors. But I then realized that my OS had been configured with a Proxy (pointing to back to a local proxy server on localhost). I uncovered this completely by accident. But when I went back to Teams after turning that local proxy off, the issues I had with the caa70004
error went away. This could explain why some people have this issue and others don't. In my case, the proxy was configured by my IT as part of the preconfiguration of my laptop.
I'm facing with issue unknownAuthError
. Please go ahead.
I'm facing with this issue on Teams Web, but Teams Desktop, it's working as well
2022-11-10T07:45:24.301Z AUTHMSAL: Attempting to handle auth response: error:token_renewal_error|Token renewal operation failed due to timeout., resource:<resource>, error mapped to action:renewalTimeout
Hello @tiennguyen1293 - Could you please share the repro steps that you have tried recently.
Also, please confirm if you have tried it with SDK V2 library?
the step:
https://teams.microsoft.com
.getAuthToken()
in the Custom App.I wasn't upgrading teams SDK v2 library, i'm using "@microsoft/teams-js": "1.11.0"
@tiennguyen1293 - Thanks for sharing the information. We will try on it and let you know the updates.
Hi,
Playing with SSO and custom tab app I notice that getAuthToken sometimes fails with renewalTimeout. When it does the only solution is to restart the whole Teams app.
I presume this is a known problem?
Using Teams Version 1.4.00.7174 (64-bit). Using Teams SDK - statics.teams.cdn.office.net/sdk/v1.8.0/js/MicrosoftTeams.min.js
Thanks, Donal