Forum Discussion
PhoneMe007
Mar 24, 2021Brass Contributor
Authenticating with an access token Connect-MicrosoftTeams
Has anyone tried authenticating with an access token (using -AadAccessToken or -MsAccessToken)? The old version of New-CsOnlineSession had an -OAuthAccessToken param, which accepted a jwt with the PS ...
- Oct 15, 2021FYI - I raised a ticket, and it should be fixed by mid november.
Issue description:
Cannot properly run Connect-MicrosoftTeams -AccessTokens
Resolution Steps:
Escalated case with our engineering Team
Issue is known bug and currently being fixed
Expecting a fix to go out by NOV mid
NMLVS
Oct 15, 2021Brass Contributor
FYI - I raised a ticket, and it should be fixed by mid november.
Issue description:
Cannot properly run Connect-MicrosoftTeams -AccessTokens
Resolution Steps:
Escalated case with our engineering Team
Issue is known bug and currently being fixed
Expecting a fix to go out by NOV mid
Issue description:
Cannot properly run Connect-MicrosoftTeams -AccessTokens
Resolution Steps:
Escalated case with our engineering Team
Issue is known bug and currently being fixed
Expecting a fix to go out by NOV mid
Andres-Bohren
Oct 26, 2021Steel Contributor
NMLVS good to hear that
- usman83Nov 04, 2021Copper Contributor
Hi,
We were successfully using Microsoft Teams powershell using Access Tokens. But today we are faced with strange issue:
We are getting error during authentication: Connect-MicrosoftTeams
The provided tokens must have less than 180 seconds difference in the time range of expiration. System.Management.Automation.RemoteException: The provided tokens must have less than 180 seconds difference in the time range of expiration.
We have checked the access tokens expiry, they do differ by more then 180 seconds. We are using Refresh tokens to generate Access tokens. This is done automatically using .NET code, both access tokens are fetched within few milliseconds, yet the expiry differs. And when we use these tokens we get above error.
Has anyone experienced this?
Regards,
Muhammad Usman
- serge2021Nov 17, 2021Copper ContributorSame problem here since a couple of days now...
Both Graph and Teams access tokens started obtaining random expiry values instead of previously static 3599 seconds.
As a quick fix, can Microsoft at least disable the tokens expiry difference verification to restore access?
Thanks. - petethemanNov 11, 2021Copper Contributor
Hi @Sridevi-MSFT,
I've also started experiencing this issue today. Was working fine before, but now I get the error: " The provided tokens must have less than 180 seconds difference in the time range of expiration."Using Teams PowerShell Module 2.3.2 with a graph token and a Teams token that are created at the same time, but the expiration time can be as great as 20min.
- ThomschNov 15, 2021Iron Contributor
- hernan-invosysNov 10, 2021Copper Contributor
usman83 Muhammad, we stating to have this same error just today:
"The provided tokens must have less than 180 seconds difference in the time range of expiration."
I've compared these 2 tokens expiration time and there are almost 7 minutes of difference between them. We ask Microsoft to generate the tokens one right after the other.If you get a solution, please share it here.
Thanks
- SajAccess4Nov 11, 2021Copper Contributor
We are having the same issue, this was working for till 10/11/2021 and it has suddenly stopped working today.