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
The microservice runs super fine before integrating with spring-cloud-netflix-zuul-websocket. But after that it stopped working.
I have observed it deeply and found that spring-cloud-netflix-zuul-websocket library is sending CONNECT request's response 'CONNECTED' back from gateway only and after that it sends the request to actual micro-service for authentication.
Expected behavior is to send it for authentication first then only allow it to be CONNECTED or DISCONNECT (based on result of auth).
Any help will be appreciated .
The text was updated successfully, but these errors were encountered:
Hi. I don't understand what you are experiencing because the CONNECT request is handled synchronously.
You can send me a sample github repo and highlight where things fail. Thanks.
I have implemented security in notification microservice by using [Web sockets with Spring and Spring Security] (https://robertleggett.wordpress.com/2015/05/27/websockets-with-spring-spring-security/)
The microservice runs super fine before integrating with spring-cloud-netflix-zuul-websocket. But after that it stopped working.
I have observed it deeply and found that spring-cloud-netflix-zuul-websocket library is sending CONNECT request's response 'CONNECTED' back from gateway only and after that it sends the request to actual micro-service for authentication.
Expected behavior is to send it for authentication first then only allow it to be CONNECTED or DISCONNECT (based on result of auth).
Any help will be appreciated .
The text was updated successfully, but these errors were encountered: