Bug 500181 - SASL authentication is done again if capability is added despite having authenticated already
Summary: SASL authentication is done again if capability is added despite having authe...
Status: ASSIGNED
Alias: None
Product: konversation
Classification: Applications
Component: protocol (show other bugs)
Version: 1.10.24122
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Konversation Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-02-16 13:00 UTC by Claire
Modified: 2025-02-16 13:39 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Claire 2025-02-16 13:00:16 UTC 
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
Comment 1 Bug Janitor Service 2025-02-16 13:39:21 UTC 
A possibly relevant merge request was started @ https://invent.kde.org/network/konversation/-/merge_requests/114