Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@johnmelodyme Web, and Janus does something completely different than what I want.
-
@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.
-
-
@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.
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/...
question
ice
stun
webrtc
oauth2.0