https://bugs.kde.org/show_bug.cgi?id=500181
Bug ID: 500181
Summary: SASL authentication is done again if capability is
added despite having authenticated already
Classification: Applications
Product: konversation
Version: 1.10.24122
Platform: Arch Linux
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: protocol
Assignee: konversation-de...@kde.org
Reporter: m...@blankeclair.slmail.me
Target Milestone: ---
SUMMARY
If the server sends something like "CAP * NEW sasl=PLAIN,ANONYMOUS",
Konversation will restart the AUTHENTICATE flow even if it has successfully
authenticated previously.
STEPS TO REPRODUCE
1. Install and setup a user in https://soju.im/
2. Connect to soju with SASL PLAIN (account "<soju username>/irc.libera.chat",
password as the soju password)
3. /msg BouncerServ network create -addr irc.libera.chat
OBSERVED RESULT
Observe that Konversation handles SASL again when the bouncer successfully
connects to Libera
EXPECTED RESULT
Konversation does not do SASL again
SOFTWARE/OS VERSIONS
KDE Frameworks Version: 6.10.0
Qt Version: 6.8.2
--
You are receiving this mail because:
You are watching all bug changes.
