Currently the blacklist and whitelist do not differentiate between clients and peers.
In certain use cases, it is desirable to differentiate between them, in example to allow clients from a certain private network to connect to a TURN server - authenticated/ authorized through the specified authentication mechanism (ephemeral/ static) - , but to restrict access to peers in the same network environment, e.g. kubernetes cluster.
Currently the
blacklistandwhitelistdo not differentiate between clients and peers.In certain use cases, it is desirable to differentiate between them, in example to allow clients from a certain private network to connect to a TURN server - authenticated/ authorized through the specified authentication mechanism (ephemeral/ static) - , but to restrict access to peers in the same network environment, e.g. kubernetes cluster.