mirror of
https://github.com/pocket-id/pocket-id.git
synced 2025-12-06 09:13:19 +03:00
🐛 Bug Report: LDAP Error #141
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @drag0n141 on GitHub.
Reproduction steps
Every time the Sync runs i get that error and no users or groups are sync.
That are my LDAP Settings.

Expected behavior
I expect that my Pocket-ID Instance sync my ldap users and groups.
Actual Behavior
Users and Groups get not synced to my Pocket-ID
Version and Environment
v1.5.0 with and ldap connection to my active directory.
Log Output
@drag0n141 commented on GitHub:
I think the problem is that objectGUID is an binary
EDIT: I am using the Settings from this issue, https://github.com/pocket-id/pocket-id/issues/553
Dont know why i am have the problem, probably because i am using postgresql and not the sqlite?
What i online found is the postgresql wants to save it as
TEXTwhen its not a valid UTF-8-Text it give this error. With SQLite it does change it variable toBLOB.@drag0n141 commented on GitHub:
@stonith404 commented on GitHub:
Could you test the
ghcr.io/pocket-id/pocket-id:dev-ldap-utf8image and let me know if this fixes the issue for you?If it does, please also share the value of
ldap_idin theuserstable.@stonith404 commented on GitHub:
@drag0n141 Thanks! Yes, that's the issue. I think the best solution would be to convert the binary GUID to a string before we save it to the DB.
@stonith404 commented on GitHub:
Please share some more information:
objectGUID?@stonith404 commented on GitHub:
Thanks for testing it. Could you pull the image again and retry it?
@drag0n141 commented on GitHub:
Now i got the error for the groups
@drag0n141 commented on GitHub:
It does work now, the users and groups are imported.
The ldap_id of one user
b07f1c06-54d3-1848-bd0c-558df97f047cEDIT: Looks like the Problem is my Browser. It does work now.
@stonith404 commented on GitHub:
Thanks, the fix should be available in the next release.