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
{{ message }}
This repository has been archived by the owner on Apr 3, 2023. It is now read-only.
CORS Error: The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include'.
#201
I have same issue...
As a result of many attempts to solve the problem, I found that the value of Keycloak Client settings "Access type" should be changed to "public".
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the bug
Error in browser when attempting to sign-in
Access to XMLHttpRequest at 'https://cnc-ac-app-qa-southcentralus-001.azurewebsites.net/realms/clicknclose/protocol/openid-connect/token' from origin 'http://localhost:3000' has been blocked by CORS policy: The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include'. The credentials mode of requests initiated by the XMLHttpRequest is controlled by the withCredentials attribute.
A clear and concise description of what the bug is.
To Reproduce
Keycloak setup
Expected behavior
No CORS error should happen when trying to log in
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: