Forum Discussion
Managing Gateway Users Failing Due to Missing 'Access-Control-Allow-Origin' CORS Header
Whenever we try to add or remove a gateway or data source user, the operation will fail after a timeout, with no message or error shown to the end-user.
In the browser console, we see messages similar to:
Access to XMLHttpRequest at 'https://wabi-west-us-redirect.analysis.windows.net/metadata/datamovement/gateways/{removed}/principals/delete?api-version=10.0' from origin 'https://app.powerbi.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.Access to XMLHttpRequest at 'https://wabi-west-us-redirect.analysis.windows.net/metadata/datamovement/gateways/{removed}/datasources/{removed}/principals?api-version=10.0' from origin 'https://app.powerbi.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.Has anyone experienced this issue before? We've been seeing this intermittently for the past year and it is extremely frustrating that we need to keep trying for a few hours or couple days to manage gateway and data source users.
3 Replies
- Hi there From your message it would appear that this is a Proxy Server error message that is coming through. Is it possible to ask your network admin if there are proxy server settings?
jmcg,
To be general, this should be an issue of HTTP error, If the server is under your control, add the origin of the requesting site to the set of domains permitted access by adding it to the
Access-Control-Allow-Originheader's value.Reference: https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS/Errors/CORSMissingAllowOrigin.
Regards,
Jimmy Tao
jmcg,
Have you solved your issue by now? If you have, could you please help mark the correct answer to finish the thread? Your contribution will be much appreciated.
Regards,
Jimmy Tao
