Difference between revisions of "Services:XMPP:SASL downgrade"
Jump to navigation
Jump to search
(Add a screenshot of Conversations to accept the SASL downgrade) |
m (Add caption) |
||
Line 5: | Line 5: | ||
== Conversations for Android == | == Conversations for Android == | ||
− | [[File:SASL downgrade.jpg|thumb]] | + | [[File:SASL downgrade.jpg|thumb|Press accept]] |
In [https://conversations.im/ Conversations], go to the account settings (the form with user address and password). After failing to connect, the 'Save' button will turn into an 'Accept' button<ref>[https://github.com/siacs/Conversations/issues/2498#issuecomment-556071993 Issue: No (obvious?) way to accept SASL downgrade]</ref>. | In [https://conversations.im/ Conversations], go to the account settings (the form with user address and password). After failing to connect, the 'Save' button will turn into an 'Accept' button<ref>[https://github.com/siacs/Conversations/issues/2498#issuecomment-556071993 Issue: No (obvious?) way to accept SASL downgrade]</ref>. |
Revision as of 13:27, 20 February 2020
See Services:XMPP for information about the kosmos.org XMPP server
We are in the process of switching over the accounts to use LDAP. However, the LDAP implementation in ejabberd doesn't support SASL authentication, which we were using before. This means that some clients will refuse to connect to the server after the switch, and display a warning about it.
Conversations for Android
In Conversations, go to the account settings (the form with user address and password). After failing to connect, the 'Save' button will turn into an 'Accept' button[1].