about federating a Rocket.Chat server

[Rainer Hoerbe]

> Am 2018-04-20 um 12:25 schrieb Peter Schober <peter.schober at univie.ac.at>:
> 
> * Corey Scholefield <coreys at uvic.ca> [2018-04-20 02:15]:
>> Has anyone here federated Rocket.Chat in a multi-party IDP setting
> 
> I think Rainer has.

Rocket.Chat can be made interoperable with a proxy. I configured SATOSA to provide following remedies:
- Lack of metadata support
- IDP-discovery, multiple IDPs
- email-type NameID (not supported by our IDPs). SATOSA does not yet support this yet, a PR is pending.
- XML-compliant namespace prefixes and ID attributes (should have been fixed by now)

- Rainer

> 
> Personally I'd suggest XMPP instead, which already is federated on the
> protocol layer, has lots of extensions that can provide a good user
> experience also with multiple clients, and has multiple available
> clients for different platforms to begin with.
> 
> If you definitively need a web frontend for XMPP I'd have suggested
> http://getkaiwa.com/ though that seems to be unmaintained these days.
> Not sure about https://www.jsxc.org/ or https://movim.eu/.
> (And no, I have no suggestion how to SAML-enable those web frontends,
> since -- just like "webmail" apps being IMAP clients -- you'll run
> into the 2-tier problem then.)
> 
> -peter
> -- 
> For Consortium Member technical support, see https://wiki.shibboleth.net/confluence/x/coFAAg
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net