The Eventbus bridge should have an Authentication message type because it's a bridge to Vert.x "Internal" messaging system. The great thing here is that Vert.x has a broad range of authentication providers and we can use them conveniently.
I emphasize that the bridge should implement authentication per connection only like what Vert.x STOMP Server already has and once the authentication is successful the client can utilize other message types to communicate as mentioned in the documentation and if it fails then send back an error message and close the connection directly.
We should support this feature to any transport like TCP, WebSocket ,SockJs and others.
Why ?
Security control from malicious attacks and any other security concerns.
What else ?
I believe we should rename the package to something like eventbus-bridge and of course the default implementation for TCP transport in addition we add SockJS event bus bridge and WebSocket event bus bridge too.
Can you contribute to this feature ?
Yes of course with little guidance from the community and the core team.
Final notes
I have developed a simpler implementation than the current and works for TCP and WebSocket with the Auth message type but we need to have further discussion before proceeding any further.
What is the feature ?
The Eventbus bridge should have an Authentication message type because it's a bridge to Vert.x "Internal" messaging system. The great thing here is that Vert.x has a broad range of authentication providers and we can use them conveniently.
I emphasize that the bridge should implement
authentication per connection onlylike whatVert.x STOMP Serveralready has and once the authentication is successful the client can utilize other message types to communicate as mentioned in the documentation and if it fails then send back an error message and close the connection directly.We should support this feature to any transport like TCP, WebSocket ,SockJs and others.
Why ?
Security control from malicious attacks and any other security concerns.
What else ?
I believe we should rename the package to something like
eventbus-bridgeand of course the default implementation for TCP transport in addition we addSockJS event bus bridgeandWebSocket event bus bridgetoo.Can you contribute to this feature ?
Yes of course with little guidance from the community and the core team.
Final notes
I have developed a simpler implementation than the current and works for TCP and WebSocket with the Auth message type but we need to have further discussion before proceeding any further.
Thanks.
@tsegismont @vietj @pmlopes