3
lorentz
4y

Has anyone here ever implemented OAuth2.0 for WebRTC? I am reading rfc7635 and its references, but they refer to functions they don't define properly and rely on cryptography jargon by eg. calling values by different names, so I'd appreciate a reference implementation of the function for building tokens to clear up the confusion.

rfc7635 on STUN extension for third-party authentication:
https://datatracker.ietf.org/doc/...

Comments
  • 0
    Oh this the ICE thing ...
  • 0
    Previously I used something called Janus Webrtc which somehow solve the issue.
  • 0
    Btw are you doing a phone application or web?
  • 1
    @johnmelodyme Web, and Janus does something completely different than what I want.
  • 0
    @homo-lorens so you are doing generic webrtc?
  • 0
    The Turn credentials I use a public one(not for production...
  • 1
    @johnmelodyme I would like a network-optimized node which is just a TURN server, and an application server that authenticates clients and gives out OAuth tokens for the TURN.
  • 0
    @homo-lorens had you tried coturn?

    https://github.com/coturn/coturn
  • 0
    @johnmelodyme Yes, the problem is how to generate the token. STUN messages are very small, so they have a special technique that makes the token a few hundred bytes, but I have trouble understanding the procedure.
Add Comment