Conversation

Notices

1. Embed this notice
   Daniel Gultsch (daniel@gultsch.social)'s status on Friday, 12-Sep-2025 23:02:43 JST Daniel Gultsch

   • JoinJabber
   • nigel

   @joinjabber @nigel @akkoma something to warn users about with these integrations is that they don't support Channel Binding (or at least I don't think they do).

   Channel Binding is something I would like to enable by default in a not too distant future and I hope that other clients move with me.

   It will still be possible to disable because there are obviously deployments where this can not be avoided but it would be nice if we could keep those to a minimum.

   • Embed this notice
     Kris (kris@outmo.de)'s status on Friday, 12-Sep-2025 23:02:38 JST Kris

     in reply to

     • JoinJabber
     • nigel
     @daniel @joinjabber @nigel I assume as long as SASL-PLAIN is the only way to achive auth integration with other system, there is really no way around that. Channel Binding is a nice feature, but personally I find it much lower priority than auth integration.
     
     Maybe you could look into supporting Oauth2/OIDC login flows in Conversations? At least Prosody seems to have good support for this now, and I think this might be the only realistic way to have both Channel Binding and auth integration.
     Kari'boka likes this.
   • Embed this notice
     Daniel Gultsch (daniel@gultsch.social)'s status on Friday, 12-Sep-2025 23:03:39 JST Daniel Gultsch

     in reply to

     • Prosody IM
     • JoinJabber
     • Kris
     • nigel

     @kris @joinjabber @nigel @prosodyim To be clear I think integrations are good. We shouldn’t prioritize between integration and channel binding and instead - from the get go - find ways to have both.

     Kari'boka likes this.
   • Embed this notice
     Daniel Gultsch (daniel@gultsch.social)'s status on Friday, 12-Sep-2025 23:03:40 JST Daniel Gultsch

     in reply to

     • Prosody IM
     • JoinJabber
     • Kris
     • nigel

     @kris @joinjabber @nigel As far as I’m aware the oauth support in @prosodyim is for authenticating other apps against existing prosody users. Meaning the user database of Prosody would be the source of truth which would allow Conversations to use channel binding. So yes I agree that this would be the better approach to integrations. But I don’t think Conversations is much involved here.