Hey!
> > I got some minor issues with it where I hope you can help me out: I
> > run a multi domain SOGo setup and therefor I am unable to provide
[...]
> Maybe we continue this discussion in your opened issue
> (https://github.com/sualko/jsxc/issues/99).
absolutely!
> > another thing concerning the php file that is used to get the turn
> > server config: 1. please, PLEASE, just make it a static json file
> > (no need to run php anywhere, especially not for static
> > configuration). 2. please do NOT put credentials in an
> > unauthenticated location
>
> You are right, currently this doesn't make sense, but I want to
> support in the next release TURN-REST-API and therefore I need a php file.
I see; so what kind of TURN server do you suggest to use and what kind of
authentication does it support?
> > 3. please, do use the same credentials for TURN authentication that
> > is used for XMPP and SOGo. This btw. is the only authentication,
> > ejabberd provides as well. (maybe add 'authentication' =
> > 'anonymous' or 'user' just like ejabberd does to the json config;
> > and then, this may go directly into the config file)
>
> I think it's a bad idea to share your sogo credentials in a json file.
> Also TURN and xmpp/sogo is totally independent.
Hmm... sorry, I think I didn't express myself well enough: ejabberd
provides a TURN server implementation that offers either no authentication
('authentication = anonymous') or the regular user backend ('authentication
user') that uses the same credentials used to log in to the xmpp service
and ultimately to log into sogo.
My idea was to add the turn server to the regular config file and use the
sogo credentials for authentication in case there is a 'turn_auth = user'
statement in the js config... (or something along these lines)
Thanks for your answer and for your support!
-- Adi
--
[email protected]
https://inverse.ca/sogo/lists
