[Bug]: User failing to join liveshare session with a 403 error
Describe the bug
For one of the tenants using our app they get a 403 error every time they try to join a liveshare sessions. The specific error is:
Error: R11s fetch error: {"message":"Invalid token validated with key2.","canRetry":false,"isFatal":false,"source":"[post] request to [http://frsprod-eastus-006-riddler] failed with [403] status code"}
We are using the liveshare react package and will see this error coming from the LiveShareContext hook:
const { joined, joinError } = useLiveShareContext()
The app will work for other tenants correctly but for this specific tenant they get a 403, it makes me lean towards something on the tenants side thats blocking this resource
But I just wanted to raise it here in case this is something yous are aware of, I'll see if I can confirm on the tenant side if they are blocking anything.
Hey @RichieMcCaff, thanks for sharing. Don't recognize this error at the top of my head. This issue appears to be returned from Azure Fluid Relay, which would imply they did receive a token from M365 but AFR rejected it. We will look into this and get back to you.
@ryanbliss Did you hear anything back on what might be causing this issue? I'm positive it's something on the users side with no-one else having this issue but they are convinced they have not done anything.
@RichieMcCaff sorry no, we weren't able to reproduce the issue. If they can get a correlation id from the teams.microsoft.com/api/platform/ api request that is failing, that would be very helpful.