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
Cannot create a new meeting, because the AutodiscoverService fails: Access to fetch at 'https://webdir2e.online.lync.com/Autodiscover/AutodiscoverService.svc/root/oauth/user' from origin 'https://5cf9b2c4cadf.ngrok.io' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled
The text was updated successfully, but these errors were encountered:
@kosgrz Is this happening with Skype online and on-prem?
Looking at this issue, it seems the client can send a specific param in its request to tell the server to return the Access-Control-Allow-Origin header. Along with this issue, this stack overflow post recommend to use the cors option with the call to app.signInManager.signIn, but I don't see this function in the plugin's code. What are your thoughts on this @kosgrz?
Cannot create a new meeting, because the AutodiscoverService fails:
Access to fetch at 'https://webdir2e.online.lync.com/Autodiscover/AutodiscoverService.svc/root/oauth/user' from origin 'https://5cf9b2c4cadf.ngrok.io' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled
The text was updated successfully, but these errors were encountered: