[jitsi-dev] locking down jitmeet


#1

Hi,

I've been experimenting with jitmeet and I'd like the list's advice on the
best way to lock it down so only authorized users can use it so that my
bandwidth bill doesn't skyrocket.

At the moment I have nginx configured with .htaccess, but I imagine there's
probably a better way to do this, maybe via attributable JIDs (instead of
the random ones currently used) when joining a MUC or something along those
lines.

Any ideas?

Cheers


#2

No this is currently not supported and an .htaccess is the most straightforward way.

It's something we'd like to have at some point though.

Cheers,
Emil

···

On 29.04.14, 20:00, Peter Villeneuve wrote:

Hi,

I've been experimenting with jitmeet and I'd like the list's advice on
the best way to lock it down so only authorized users can use it so that
my bandwidth bill doesn't skyrocket.

At the moment I have nginx configured with .htaccess, but I imagine
there's probably a better way to do this, maybe via attributable JIDs
(instead of the random ones currently used) when joining a MUC or
something along those lines.

--
https://jitsi.org


#3

there is actually a login form that is hidden, if you pass the right things into https://github.com/jitsi/jitsi-meet/blob/master/app.js#L66
and your xmpp server is configured with normal accounts instead of anonymous authentication things should just work.

···

Am 29.04.2014 20:00, schrieb Peter Villeneuve:

Hi,

I've been experimenting with jitmeet and I'd like the list's advice on the
best way to lock it down so only authorized users can use it so that my
bandwidth bill doesn't skyrocket.

At the moment I have nginx configured with .htaccess, but I imagine there's
probably a better way to do this, maybe via attributable JIDs (instead of
the random ones currently used) when joining a MUC or something along those
lines.

Any ideas?


#4

Thanks Philipp,

That was the sort of "neat" solution I was thinking of. I'll take a look.

···

On Tue, Apr 29, 2014 at 7:30 PM, Philipp Hancke <fippo@goodadvice.pages.de>wrote:

Am 29.04.2014 20:00, schrieb Peter Villeneuve:

Hi,

I've been experimenting with jitmeet and I'd like the list's advice on the
best way to lock it down so only authorized users can use it so that my
bandwidth bill doesn't skyrocket.

At the moment I have nginx configured with .htaccess, but I imagine
there's
probably a better way to do this, maybe via attributable JIDs (instead of
the random ones currently used) when joining a MUC or something along
those
lines.

Any ideas?

there is actually a login form that is hidden, if you pass the right
things into https://github.com/jitsi/jitsi-meet/blob/master/app.js#L66
and your xmpp server is configured with normal accounts instead of
anonymous authentication things should just work.

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev