From mboxrd@z Thu Jan 1 00:00:00 1970 From: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=20161023; t=1609119539; bh=ApcFs+BMLrXgdDy7ZLm4bWwd8UsIa5XMTd5ARQv02B0=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=SJUjW2P88pGR+hdAnGFUrZahmaB3oxOV/mBKQqDve1PNFa2uWgsxF8KIF0tp7Ea2L Dka2/QZw0zOITSr+iB2QyfAG5RJBV91NUELLRGEiw2f3dN2toc/pL1bn0YnO6SLMCr qBYzu+x5owOfYS8nYxgL5sOsQ0LXE/B6c798c8uaI7St0yLeU9S7jD3OZzkd2iEBpt 3SLoK33LN+fqcWNIXv2aH0X9zv8IFTiw3Pgtz2IjoucNzZZeREIJrUeKJVVqeS/bI4 JKSB/bpghgb8QFrnt5qpHQ6Z/8MWvcSqCe9NHsYjapJ8Rm0V/IxUWzDgeCOTF22QdH UnQ8E9q/CdHlw== To: Juliusz Chroboczek In-Reply-To: <87r1nau8v0.wl-jch@irif.fr> References: <1082cfcde178ddb72b51bcd03ee6770a@kn1ght.org> <87zh1zt6ip.wl-jch@irif.fr> <87y2hjt5fx.wl-jch@irif.fr> <87y2hjxa64.fsf@toke.dk> <87r1nau8v0.wl-jch@irif.fr> Date: Mon, 28 Dec 2020 02:38:57 +0100 X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <87sg7qyaj2.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Message-ID-Hash: GERVNY7SGOMO3XNMR6NKP4MRLTZHU3K6 X-Message-ID-Hash: GERVNY7SGOMO3XNMR6NKP4MRLTZHU3K6 X-MailFrom: toke@toke.dk X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; suspicious-header CC: Cell , galene@lists.galene.org X-Mailman-Version: 3.3.2 Precedence: list Subject: [Galene] Re: coturn config List-Id: =?utf-8?q?Gal=C3=A8ne_videoconferencing_server_discussion_list?= Archived-At: List-Archive: List-Help: List-Post: List-Subscribe: List-Unsubscribe: Juliusz Chroboczek writes: >> Well presumably the REST web server will only respond to the WebRTC serv= er > > Ah... so the WebRTC signalling server only communicates the ICE > configuration once a client has authentified. That was the bit I was > missing. > > In Gal=C3=A8ne, authentication only happens when you join a group, so that > would mean communicating the ICE configuration together with the "joined" > message that carries the client's permissions. Yup, that makes sense! >> (in coturn you specify an API key)? > > Ah, I see. Section 2.1 of the draft. > > Thanks, Toke, it makes a lot more sense now. You're welcome - I look forward to your implementation :) -Toke