LDAP 인증 오류 – ActiveSupport::MessagePack::UnserializableObjectError

기여 버그
1

Hi everyone,

I’m using the discourse-ldap-auth plugin on a self-hosted Discourse (Docker install).
After a recent rebuild, LDAP authentication started failing for all users.

Here’s the relevant error from production.log:

(ldap) Authentication failure! ldap_error: ActiveSupport::MessagePack::UnserializableObjectError,
Unsupported type Net::BER::BerIdentifiedString for object “******** (Kullanıcı Teknolojileri Yönetim Müdürlüğü)”
Started GET “/auth/failure?message=ldap_error&origin=http%3A%2F%2Fic*ot*rol.va**fb*nk.intra%2Flogin&strategy=ldap”
Processing by Users::OmniauthCallbacksController#failure as HTML
Completed 200 OK

Details

  • The issue affects all LDAP users.

  • All users in our LDAP directory have displayName values containing Turkish characters (ğ, ü, ş, İ, etc.).

  • The error occurs right after the LDAP authentication attempt — no user gets logged in.

image
image1673×182 22.4 KB

Is this a general problem with the latest version of Discourse? Could it be related to a Ruby incompatibility? What solution do you suggest?

1개의 좋아요
2

Hello everyone and Osmanmermer,
We have had the same error here for a few days:
(ldap) Authentication failure! ldap_error: ActiveSupport::MessagePack::UnserializableObjectError, Unsupported type Net::BER::BerIdentifiedString for object "username"

  • The problem currently affects newly created LDAP users who have never logged in before.
  • It is independent of special characters.
1개의 좋아요
3

최근에 도입된 버그일 수 있으므로, 비슷한 방식으로 두 사이트가 영향을 받은 것으로 보아 Contribute > Bug 채널로 옮겼습니다.

지난주 이후로 사용자 측에서 변경된 사항이 있나요? 업데이트를 다시 실행한 후 문제가 해결되었나요?

4

Oops just noticed this is not an official plugin so not officially supported. I also am not immediately finding the plugin topic. We should move this into there. Can someone help find it? I am on the move currently and not at my desk.

1개의 좋아요
5

Hello, it concerns the update to 3.6.0.beta2 and the error only affects newly created accounts (Ldap user create mode) for us. Existing accounts can still log in. Rolling back to 3.6.0.beta1 resolves the issue. The LDAP Auth Plugin has not changed.

6

Sorry to hear you’re having trouble! Unfortunately the LDAP auth plugin is not written by us at Discourse and so is not supported. It does not even have a Customization > Plugin topic here. If you need help with it, contact the author on github or start a Marketplace topic to see if an expert in the community is up to the task.