-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Blather does not authenticate existing user #151
Comments
If I understand correctly, #106 suggests disabling in-band registration server-side. That changes the 409 error to a 403 everywhere. #114 suggests downgrading from blather 0.8.5 to 0.8.4. Dunno about those old versions, but the problem exists with both blather 1.0.0 and 1.1.4. As to different versions of ejabberd, I believe this problem first arose upon upgrading ejabberd. I'm not sure which version it broke with: it definitely worked in ejabberd 14.07, and definitely not with 15.09 or 15.07. So somewhere in between ... (14.12, 15.02, 15.03, 15.04 or 15.06). |
Since the only way to be sure why this is happening is to figure out which version broke it, and that that may take a while, I'd ask that you do that and let us know as accurately as you can what changed. Working logs for comparison would also help. |
Disabling (entirely) |
And, since you asked for a working log, with
|
If you have a working log with mod_register enabled on an older version of ejabberd, I'd love to see that also. |
Sorry, but that won't be particularly easy. Still, it's clear what's going on:
I think blather ought to try an |
Yes, it should. Do you fancy submitting a failing spec to show the issue? |
the same problem with prosody here, I'm unable to disable registre module |
Here's a simple blather script which sends a message to a user:
As I understand the documentation, Blather should first attempt to authenticate as the user 'my_user' and then, if authentication fails, it should attempt to use in-band registration to register 'my_user' as a new user.
With ejabberd 15.09, that's not what happens:
Note: here, the 403 is because in-band registration is disabled for remote clients. On localhost, where in-band registration is permitted, one gets instead
because the user 'my_user' already exists.
The text was updated successfully, but these errors were encountered: