#843 [mod_websocket] auth fails if wrong credentials are provided initially

Reporter mt
Owner Zash
Created
Updated
Stars ★ (1)  
Tags
  • Priority-Medium
  • Status-CantReproduce
  • Type-Defect
  1. mt on

    What steps will reproduce the problem? 1. Try to login with a client via websocket and accidentally issue a wrong password 2. Realize your error and enter the correct password 3. Never get connected unless you reload the page What is the expected output? What do you see instead? Login should succeed. What version of the product are you using? On what operating system? Debian Jessie Prosody 0.10 nightly build 356 (2017-03-04, 8acc35b5355a) prosody-modules rev: 08f2d2a61af8 Possible issue: In the chrome debug log you can see that converse tries to bind the resource but never receives a reply from prosody. <iq type="set" id="_bind_auth_2" xmlns="jabber:client"><bind xmlns="urn:ietfarams:xml:ns:xmpp-bind"><resource>converse.js-20611459</resource></bind></iq> Related converse.js issue https://github.com/jcbrand/converse.js/issues/618 Thanks to jcbrand for looking into the issue.

  2. Zash on

    Hi, thanks for the report. Can you please provide debug logs from Prosody, along with configuration.

    Changes
    • tags Status-NeedInfo
    • owner Zash
  3. mt on

    Sorry for the late response, i am not able to reproduce the error with a clean lab setup. The original instance is not available any more and the setup was rather complicated so it might have been a configuration issue.

  4. Zash on

    Well then, not much to do then. Thanks anyways.

    Changes
    • tags Status-CantReproduce

New comment