W3C home > Mailing lists > Public > public-webrtc@w3.org > August 2016

Re: Issue 714: STUN/TURN OAuth token auth parameter handover

From: Bernard Aboba <Bernard.Aboba@microsoft.com>
Date: Mon, 15 Aug 2016 17:46:54 +0000
To: "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-ID: <DM2PR21MB0075890410D29B3DA5978392EC120@DM2PR21MB0075.namprd21.prod.outlook.com>

Today we have:

dictionary RTCIceServer {

    required (DOMString or sequence<DOMString>) urls;

             DOMString                          username<http://w3c.github.io/webrtc-pc/#dom-rtciceserver-username>;

             DOMString                          credential<http://w3c.github.io/webrtc-pc/#dom-rtciceserver-credential>;

             RTCIceCredentialType               credentialType = "password";


enum RTCIceCredentialType {




This issue asks how (or if) this can be used to support RFC 7635<https://tools.ietf.org/html/rfc7635> (OAuth 2.0) when credentialType = "token".

An example of an access token is given in RFC 7635, Appendix B:











Rather than adding new attributes to RTCIceServer (as proposed in Issue 714), is there a reason why such a token couldn't be passed in RTCIceServer.credential with RTCIceServer.credentialType = "token"?
Received on Monday, 15 August 2016 17:47:25 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:49 UTC