RyanN.83801 (Customer) asked a question.
Getting CORS errors when connecting signalR to React App
When the React app starts up and log into okta, we connect the signalR hub to the frontend. However, we're getting this CORS error. As you can see, the origin is the same as the resource. We are using the Okta SPA for the front end and have a backend service handling signalR and other API endpoints using Okta. Our backend service is connected to Okta on startup like so
Both the frontend and backend are using the same custom Okta Authorization Server/issuer id
Hello @RyanN.83801 (Customer) Thank you for reacting out to our Community!
The error seems to be indicating CORS origin is being blocked, you might want to allow CORS origin in Okta. Please see the attached doc on how to do this:
https://developer.okta.com/docs/guides/enable-cors/main/
If this does not help resolve the issue please leverage the Okta Developer forums for this type of questions and take advantage of their expertise.
https://devforum.okta.com/
Hope this helps and if this answered your question, please mark this as Best Answer!
We added both urls as trusted CORS origin in Okta but still seeing this error. Notably, this only happens when signalR connection starts. Are there any examples of Okta implemented with a signalR application?
@RyanN.83801 (Customer) Please see this doc that might provide some insight:
https://github.com/okta/okta-aspnet/issues/71