-
FEATURED COMPONENTS
First time here? Check out the FAQ!
1 | initial version | |
I found the problem: we use keycloak as user management and authentication service. There is a problem with cross origin ajax requests.
Access to fetch at 'http://...' (redirected from 'http://.../zkau') from origin 'http://...' 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.
Anybody aware of this problem? Do I need to configure zk properly to allow this "access"?
2 | No.2 Revision |
I found the problem: we use keycloak as user management and authentication service.
There is a problem with cross CORS (cross origin resource sharing) ajax requests.
Access to fetch at 'http://...' (redirected from 'http://.../zkau') from origin 'http://...' 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.
Anybody aware of this problem? Do I need to configure zk properly to allow this "access"?