[GH-ISSUE #268] Standardise the images #100

Closed
opened 2026-02-27 08:15:15 +03:00 by kerem · 3 comments
Owner

Originally created by @grehund on GitHub (Jul 25, 2022).
Original GitHub issue: https://github.com/lldap/lldap/issues/268

Is there a plan to standardize the images so we don't have a user field of cn in :latest and uid in :stable?
My understanding is that uid is the desired field long-term.

Originally created by @grehund on GitHub (Jul 25, 2022). Original GitHub issue: https://github.com/lldap/lldap/issues/268 Is there a plan to standardize the images so we don't have a user field of `cn` in `:latest` and `uid` in `:stable`? My understanding is that `uid` is the desired field long-term.
kerem 2026-02-27 08:15:15 +03:00
  • closed this issue
  • added the
    invalid
    label
Author
Owner

@nitnelave commented on GitHub (Jul 25, 2022):

Are you sure you have the latest :latest, did you pull again? uid had been a user field for quite some time now.

<!-- gh-comment-id:1193616818 --> @nitnelave commented on GitHub (Jul 25, 2022): Are you sure you have the latest `:latest`, did you pull again? `uid` had been a user field for quite some time now.
Author
Owner

@grehund commented on GitHub (Jul 25, 2022):

if I tell Nextcloud LDAP to use uid it (Nextcloud) constantly logs errors. if I tell it cn = no errors. I'm frustrated that everything i read seems to contradict the last thing I read and the biggest doubt I have always seems to come back to LLDAP. I now have a problem with Authelia authenticating against LLDAP.

<!-- gh-comment-id:1193623621 --> @grehund commented on GitHub (Jul 25, 2022): if I tell Nextcloud LDAP to use `uid` it (Nextcloud) constantly logs errors. if I tell it `cn` = no errors. I'm frustrated that everything i read seems to contradict the last thing I read and the biggest doubt I have always seems to come back to LLDAP. I now have a problem with Authelia authenticating against LLDAP.
Author
Owner

@nitnelave commented on GitHub (Aug 22, 2022):

Sorry to come back to the charge, but :latest has had uid for strictly longer than :stable :)
The only possibility is if you didn't pull :latest again.

I'm closing this issue, feel free to create a new one with other problems that you find.

<!-- gh-comment-id:1222511770 --> @nitnelave commented on GitHub (Aug 22, 2022): Sorry to come back to the charge, but `:latest` has had `uid` for strictly longer than `:stable` :) The only possibility is if you didn't pull `:latest` again. I'm closing this issue, feel free to create a new one with other problems that you find.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/lldap-lldap#100
No description provided.