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
We have identified a need to implement a mechanism to block duplicate service registrations in the MicroStream Hub. Currently, there is no functionality to prevent multiple instances of the same service from connecting to the hub, which can lead to potential conflicts and security issues.
Note: The client-side implementation of this feature is being tracked in Issue #3 in the client repository.
Steps to Reproduce:
Start the MicroStream Hub.
Connect a service with a specific name (e.g., serviceA).
Attempt to connect another service with the same name (serviceA).
Observe that both services are able to connect without any restrictions.
Expected Behavior:
The hub should reject any duplicate service registration attempts and prevent multiple instances of the same service from connecting.
Actual Behavior:
The hub allows multiple instances of the same service to connect without any restrictions.
Impact:
This issue can lead to potential conflicts and security vulnerabilities in the MicroStream Hub.
The text was updated successfully, but these errors were encountered:
## [1.0.6](v1.0.5...v1.0.6) (2025-03-01)
### Bug Fixes
✅ **hub.js:** prevent duplicate service registration in hub ([9b3168f](9b3168f)), closes [#3](#3)
- Added socket.io middleware to validate service registration
- Implemented service name uniqueness check during connection
- Added standardized error response for duplicate registration attempts
- Implemented socket cleanup for rejected connections
- Added proper logging for duplicate registration attempts
- Implemented automatic rejection of duplicate socket connection requests
This prevents multiple services from registering with the same name, ensuring message routing integrity and system stability. Any duplicate connection attempts are automatically rejected at the connection level, providing enhanced security against unauthorized service impersonation. <br/><br/>
We have identified a need to implement a mechanism to block duplicate service registrations in the MicroStream Hub. Currently, there is no functionality to prevent multiple instances of the same service from connecting to the hub, which can lead to potential conflicts and security issues.
Note: The client-side implementation of this feature is being tracked in Issue #3 in the client repository.
Steps to Reproduce:
Start the MicroStream Hub.
Connect a service with a specific name (e.g., serviceA).
Attempt to connect another service with the same name (serviceA).
Observe that both services are able to connect without any restrictions.
Expected Behavior:
The hub should reject any duplicate service registration attempts and prevent multiple instances of the same service from connecting.
Actual Behavior:
The hub allows multiple instances of the same service to connect without any restrictions.
Impact:
This issue can lead to potential conflicts and security vulnerabilities in the MicroStream Hub.
The text was updated successfully, but these errors were encountered: