I have a nodeJS express app, that serves front end app using React and also provides an API. The React app calls the backend API and as such there is no cross origin.
When I deploy this to Bluemix without SSO, everything works fine. When I deploy using SSO service I get error
Fetch API cannot load https://abcd-9bgrvudk1p-ct20.iam.ibmcloud.com/idaas/oidc/endpoint/default/authorize?response_type=code&client_id=Z4eSiL50dT&redirect_uri=https%3A%2F%2Fconsole-sso.mybluemix.net%2Fauth%2Fsso%2Fcallback&scope=openid%20openid.
No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'https://console-sso.mybluemix.net' is therefore not allowed access. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.
I tried calling the API directly and after SSO auth, it works fine, But when the API is invoked by the front end app, it returns the above error.
FYI, API target is https://console-sso.mybluemix.net/api/reports/daily-reports
I have followed the Single Sign On documentation
I tried adding CORS module and response headers to allow a CORS request but it did not work. I also tried adding * to SSO configuration to allow all origins but no luck. Any pointers would be great! Thanks
This will require Support to review. Please open a ticket with the BlueMix support team
Related
I have my Express API server as well as the SPA hosted on Heroku. The SPA uses Azure ad authentication using MSAL. The APIs are secured using Passport-azure-ad. Everything was working well in my localhost and the requests made where getting a success response. However on uploading the changes to Heroku I am now getting the CORS error. I have registered the API on Azure AD and exposed the API to my SPA. Any reason why I am still getting the error?
Access to fetch at 'https://myTestApp-server.herokuapp.com/getUsers' from origin 'https://myTestApp.herokuapp.com' 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.
To avoid the CORS error, make sure to add the header like below:
While adding the Allowed origins use * to allow all like below:
Otherwise, add particular origins like below:
Make sure to restart the Api after making the above changes.
Check whether you are using correct version of NodeJs that matches the runtime you’re developing and testing.
Try modifying CORS policy by adding .SetIsOriginAllowed((host)=> true)"
If you are adding header via Nodejs code make use of below command:
res.setHeader('Access-Control-Allow-Origin', '*');
Or
res.setHeader('Access-Control-Allow-Origin',
https://myTestApp-server.herokuapp.com:4200');
For more in detail, please refer below link:
Azure App Service No ‘Access-Control-Allow-Origin’ header is present
No 'Access-Control-Allow-Origin' header is present on the requested resource in angular app
3 Ways to Fix the CORS Error and How the Access-Control-Allow-Origin Header Works
I'm having a problem with my React / ASP.net core web API app and authentication with Azure AD.
The first time I log in it's all fine. Then if I sign out, I get presented with the Microsoft hosted "You have been signed out. Return to the website" page, which has a link back to the site.
If I then click on that link then the app hangs when it tries to authenticate, and I'm getting CORS errors in my Chrome browser console:
Access to fetch at
'https://login.windows.net/XXXXX/oauth2/authorize?response_type=id_token&redirect_uri=
(etc)' (redirected from
'https://uat.xxxxx.com/coreservice/api/foo?page=1&pageSize=25') from
origin 'https://uat.xxxxx.com' has been blocked by CORS policy:
Response to preflight request doesn't pass access control check: 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.
Extra info:
As an experiment I hosted a link to the site from elsewhere on the web and I get the same problematic behaviour if I click on that link.
If I hard refresh the page at this point, then it all works fine - I'm presented with the MS Azure login page as expected.
Any help would be gratefully received!
Not sure if you are using the Azure Web Apps to host your application, but the issue I had was that I was using the App Service Authentication setting under Authentication/Authorization in the Azure Portal. This setting was pointing to the Azure AD instance. But I also was using React-ADAL npm package wrapped around my application so it was causing conflicting issues since they were both using the same instance of Azure AD.
I turned off the App Service Authentication setting in the Azure portal and everything worked from there.
This setting does work as I have used it with other applications and simple web apps but I realized that the Azure App Auth setting was conflicting with the React-ADAL npm package.
Hope this helps.
I am trying to get the nodeJS keycloak adapter working with my Express application, but am facing a CORS issue when it tries to redirect to the login page for routes I have protected with the keycloak middleware:
XMLHttpRequest cannot load
http://192.168.132.44:8080/auth/realms/Actora/protocol/openid-connect/auth?client_id=actora-test&state=0e9c9778-c41b-4aa8-8052-d0f0125045ac&redirect_uri=http%3A%2F%2Flocalhost%3A5001%2Fauth%2Fchecktoken%3Fauth_callback%3D1&scope=openid&response_type=code.
Response to preflight request doesn't pass access control check: No
'Access-Control-Allow-Origin' header is present on the requested
resource. Origin 'http://localhost:5001' is therefore not allowed
access.
In my keycloak client settings I have added a single value of '*' to the Web Origins config section.
I have also enabled cors on my node express application using the node cors library, following this express guide here
var cors = require('cors'),
app = express();
app.use(cors());
app.options('*', cors()); //enable for all pre-flight requests
I using version 3.2.1 of keycloak in case that makes any difference (I see a new version is out as an RC)
Has anyone faced similar issues and managed to resolve? I have been digging through many JBOSS mailing list threads and other stackoverflows, and all seem to suggest its as simple as adding the '*' entry to the web origins config section for the client on the keycloak admin site but this is not the case for me.
Thanks
I am also working on this issue with mindparse.
I think the key issue here is that the keycloak server is not responding with any ACCESS-CONTROL-ALLOW-ORIGIN headers despite the fact that he has correctly configured the "web Origins" setting in the keycloak admin portal.
A more in depth flow of the process is:
The user attempts to call a keycloak secured route on a node express server
Keycloak middleware detects that the user is not authenticated and
responds to the request with a 302 (redirect) to a custom login page hosted
by the keycloak server.
The browser sends an OPTIONS request to the keycloak server to check if it is
because it is a cross origin request.
The keycloak servers response DOES NOT include the ACCESS-CONTROL-ALLOW-
ORIGIN header to tell the browser that it has permission to make this
request.
The browser then reads this response and therefore does not make the follow
up request because it did not pass the access control allow origin checks
Just put the url of your app like "http://localhost:8081" in "Web Origins" field of client settings in Keycloak.
I had the exact same problem. I am using Keycloak 6.0.1
In my case, I had to add "enable-cors": true in keycloak.json in my Java backend server.
Afterward, I had another issue: 401 UNAUTHORIZED.
This post solved the problem
Web Origins must be set correctly for a configured client, yes, but it too has some pitfalls because a "+" setting depends on other values.
E.g., I had this wrong configuration for local tests:
Root URL: http://localhost:3000/
Valid redirect URIs: *
Web Origins: +
... and it failed with a CORS issue like you describe.
The issue lay with the other two settings, so this is correct and works now:
Root URL: http://localhost:3000
Valid redirect URIs: /*
Web Origins: +
(The KeyCloak UI is a usability nightmare on many fronts, imo, this is just one pitfall)
I also faced CORS issues while trying to connect to KeyCloak, even though I had correctly filled out the "Web Origins" url.
Turned out I accidentally connected to the wrong App (Client) and tenant (Realm), therefore not passing the CORS checks. Pointing to the right app and tenant fixed my problem.
Hi I am calling an Azure Application Proxy endpoint (myapp.msappproxy.net) through the browser and am running into a CORs issue. How/where can I configure CORs for the Azure Application Proxy endpoint? I've looked in both the old and new Azure portals.
The error I'm getting is on the OPTIONS preflight request.
XMLHttpRequest cannot load https://myapp.msappproxy.net. Response for
preflight is invalid (redirect)
I realize that you set the access-control headers on the API endpoint, in this case the App Proxy, but I can not find where to do so. Additionally, I must set a custom header in my request, because am using bearer token authentication.
Thanks!
Just had the same issue. I have an Azure Application Proxy. So an internal page is available for externals. But normally the Application Body is set to No. With that setting browsers having huge CORS errors. To fix these CORS problems you have to set the Application Body to Yes. Now the body is correctly set and all browsers are able to show the website without CORS issues.
Also good hints you can find in the Enable link translation section.
I am using Azure DocumentDB with REST API and trying to call the API from HTML page using Ajax requests. But I found that authorization headers are not getting added in a request. After searching, a lot, I found that it may be a CORS issue. Same request works well when POSTMAN tool is used. Security header got set in this case.
You're correct! DocumentDB REST API can't be called using AJAX from the browser because of CORS and right now it is not possible to configure CORS settings for a DocumentDB account.