-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Internal server error on login with ldap_auth_provider #2678
Comments
I can confirm the issue |
Me too |
thanks. This was introduced in 4c8f94a. |
Hi, thanks for the quick fix. Update: Is downgrading even possible? Update2: eded708 seems to be an easy fix. I added the fix to /usr/lib/python2.7/dist-packages/synapse/handlers/auth.py and deleted the auth.pyc and recompiled it, but still no luck. What else has to be changed? Update3: Ok I figured it out, this fix 6f05de0 is also necessary. Now it's up and running again. |
Hi, I now updated to 0.25.1 but this fix is missing: 6f05de0 Without this I still get:
|
This fix 6f05de0 is still missing for me in the debian package 0.26.0-1. |
@rexometer did you have upgraded your synapse app to the last version ? Because since 4 month ago the app moved from the debian package to pythonvirtualenvironnement. |
thanks @Josue-T for the fast reply. Not sure, I installed it via package-manager (added the repo http://matrix.org/packages/debian/) maybe 1,5 years ago and always updated it via apt-get. What else is needed to correctly update it? |
This affects me as well, I've followed the pip upgrade guide and I can't issue new logins through LDAP. My log only show me the 500 though it doesn't show me the trace from python, please instruct me on how to find more specific log entries. matrix-synapse (0.26.0) |
For the record: this issue (internal server error) was introduced in v0.25.0 by 4c8f94a and fixed by #2679 in v0.26.0. I have opened (and closed) a separate issue #2912 for the problem mentioned by @rexometer. @Josue-T wrote:
I don't know what this is referring to, and it doesn't really make much sense. There has been no moving of anything from a debian package to anywhere else. If you have installed with debian, then please continue to upgrade via debian - attempting to use pip to upgrade an installation made by the debian package will certainly lead to brokenness. @misse you'll get better support for synapse administration in the matrix rooms than by commenting on a resolved issue, but your |
Thanks @richvdh My homeserver.log doesn't show the stack trace and I still have the issue that is supposed to be fixed. I.e. I can't log in users via LDAP, I get the m_unknown message for riot but can't find anything else. I'll try to join the synapse admin room to figure this out. |
Issue solved by upgrading rest_auth_provider.py to the latest version (46e68c4cbeb4c027cf4d65e4ae883fdabe8762c1), upgrading mxisd to 0.6.1 and restarting synapse |
Description
Cannot login or perform action require auth, if synapse using ldap_auth_provider.
Steps to reproduce
use ldap_auth_provider
Version information
If not matrix.org:
The text was updated successfully, but these errors were encountered: