Monday, March 10, 2025
3 changes · saas-18.1
Resolved issues and error corrections
Users signing in with passkeys will no longer be asked to complete a captcha during login. Captcha checks still apply to password logins, keeping brute-force protection where it is needed while making passkey login smoother.
Original PR description
Before this commit a captcha would always be required upon submitting to /web/login. This makes sense to prevent brute force attacks against passwords. However this does not make sense in the context of webauthn. Therefore we make sure captcha is only verified when using the password credential type.
This fix makes Odoo's live chat more reliably connect visitors to the messaging channel after a chat is created. It reduces the chance that a timing issue prevents guest users from receiving chat updates, helping conversations start and continue smoothly.
Original PR description
Since [1], bus subscription to the guest channel is only made explicitly in the CORS bundle. However, race conditions can occur leading to the subscription not being made. This PR ensures we always subcribe to the guest channel. [1]: https://github.com/odoo/odoo/pull/199779 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Live chat channel invitations now show the configured live chat operator name instead of exposing the real user name. This keeps customer-facing chat messages consistent with the live chat setup and avoids confusing or unintended operator identity display.
Original PR description
Before this PR, the real live chat operator name was shown on the channel join notification. The issue is that the name is stored in the message in database, which does not allow configuration according to who's seing the message. A decent solution is to always store the live chat user name if any, which comes with some downsides such as not being able to update the messages afterwards. However, live chat conversations are short lived which mitigates the issue. Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr