authorization mechanism/ webrtc compatibility?

[andrewvmail]

Just wondering is this using the same mechanism proposed in this slide? https://www.ietf.org/proceedings/87/slides/slides-87-behave-10.pdf (the stateless auth or the typical turn auth)

for some reason i can't get it to work trying to swap coturn with mongooseice (using stateless auth)

I also tried it using this demo to test the mongooseice https://webrtc.github.io/samples/src/content/peerconnection/trickle-ice/

i left the username empty based on the guide here https://mongooseim.readthedocs.io/en/latest/user-guide/ICE_tutorial/ but not sure what to do with how to set the realm using webrtc protocol

[rslota]

Hi @andrewvmail ,

Currently MongooseICE supports only standard STUN/TURN long-term credentials - when running from docker, whatever you set as MONGOOSEICE_STUN_SECRET will be your "password" in WebRTC. The username can be whatever you like, as it's not used right now in any way other then to check ownership of TURN Allocations, which only means that it should be constant across all your requests from a single client.

This obviously is not ideal. Eventually we will introduce some kind-of short term credential system, that for sure will result in some HTTP APIs (as this part is not regulated by any of ICE standards). PRs will proposals are very welcome :)