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
I noticed the clientId is a readonly property of the Client interface. However, very often the client id is used as an active part of the communication, e.g. for security reasons a filter is implemented and a specific client id must be set in a given network.
There is a comment saying that the id is only used for logging, which is not the case, as can be seen here:
So ideally I would suggest the client id should be part of ClientOptions.transport along with all other settings. At very least it should be made writable, to avoid hacks like those:
Hello,
I noticed the
clientId
is a readonly property of theClient
interface. However, very often the client id is used as an active part of the communication, e.g. for security reasons a filter is implemented and a specific client id must be set in a given network.There is a comment saying that the id is only used for logging, which is not the case, as can be seen here:
vda-5050-lib.js/src/common/client.ts
Line 1062 in 907ff69
So ideally I would suggest the client id should be part of
ClientOptions.transport
along with all other settings. At very least it should be made writable, to avoid hacks like those:what do you think?
The text was updated successfully, but these errors were encountered: