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 Jul 16, 2024. It is now read-only.
Describe the bug
I'm having a problem making a connection from rsocket-js to the broker via websocket.
When creating connection from client to broker with access token error. The authenticationService is still working properly, the returnRejectedRsocket function is still being called. However, the client side still reports successful connection before the 'returnRejectedRsocket' result is returned from the broker.
The client will receive an error message when making a subsequent request.
Environment
Alibaba RSocket Broker version: 1.1.3
Operating System version: Windows 10
Java version: 11
Steps to reproduce this issue
enable authentication require from broker
make a connection from web using rsocket-js. add token error to metadata
Pls. provide GitHub address to reproduce this issue.
Expected Result
I expect to receive an error result
Actual Result
Client receive connect succeed from broker.
The client will receive an error message when making a subsequent request.
The text was updated successfully, but these errors were encountered:
Describe the bug
I'm having a problem making a connection from rsocket-js to the broker via websocket.
When creating connection from client to broker with access token error. The authenticationService is still working properly, the returnRejectedRsocket function is still being called. However, the client side still reports successful connection before the 'returnRejectedRsocket' result is returned from the broker.
The client will receive an error message when making a subsequent request.
Environment
Steps to reproduce this issue
Pls. provide GitHub address to reproduce this issue.
Expected Result
I expect to receive an error result
Actual Result
Client receive connect succeed from broker.
The client will receive an error message when making a subsequent request.
The text was updated successfully, but these errors were encountered: