Skip to content
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

OpenLDAP v2.6 #670

Open
guillelb opened this issue Nov 6, 2023 · 9 comments
Open

OpenLDAP v2.6 #670

guillelb opened this issue Nov 6, 2023 · 9 comments

Comments

@guillelb
Copy link

guillelb commented Nov 6, 2023

Hello,
I see that there have been no changes to the repo for two years now. The OpenLDAP version has advanced to the current v2.6.6, but this repo is still using v2.4.
Do you plan to update the OpenLDAP version?

@zerowebcorp
Copy link

I'm also wondering if it is still being maintained. I see a lot of people are moving to Bitnami image, probably because of this reason.

@bignay2000
Copy link

@BertrandGouny This is an amazing repo. Why let this die!

@bignay2000
Copy link

@dbck 10 Million downloads on docker hub. Just need this updated!

@polarathene
Copy link

polarathene commented Jul 1, 2024

I see a lot of people are moving to Bitnami image, probably because of this reason.

Yeah, I don't think it's being maintained here. bitnami/openldap has been good, but I've only really used it in our test suite where LDAP support doesn't have much coverage. Actively maintained though 👍


Just for anyone interested, I migrated from this Docker image a while back, I looked into a few options and documented that and chose to switch to bitnami/openldap.

Below is a rough guide you could probably follow (see the linked PR for additional details in switching if helpful), in case it helps anyone else :)


Example adapted from usage in DMS CI test suite:

# Setup a local openldap service:
docker run --rm -d --name ldap-example \
  --env LDAP_ADMIN_PASSWORD=admin \
  --env LDAP_ROOT='dc=example,dc=test' \
  --env LDAP_PORT_NUMBER=389 \
  --env LDAP_SKIP_DEFAULT_TREE=yes \
  --volume "path/to/openldap/ldifs/:/ldifs/:ro" \
  --volume "path/to/openldap/schemas/:/schemas/:ro" \
  --hostname 'ldap.example.test' \
  bitnami/openldap:latest

Example volumes for LDIFs here: https://github.com/docker-mailserver/docker-mailserver/tree/22383c28e7cf6d38b674f8a0d28ff522bbad3929/test/config/ldap/openldap/ldifs

@EugenMayer
Copy link

EugenMayer commented Oct 22, 2024

Just in case anybody in here is still waiting for the good news, the company behind this image does no longer exist: https://www.osixia.net/

UPDATE (correction)
The company still exists, but the repo/image is no longer maintained, see @BertrandGouny statement below

@BertrandGouny
Copy link
Member

The company is more alive than ever and never had a website... the domain is used for email and internal tools. Just not maintening open source repo for now.

@EugenMayer
Copy link

So this was the only way to let you respond by (sorry, falsly) stating the company has been shutdown? People now asked several times, a couple of forks have been created all without any hints.

Do not get me wrong, i'am very thankful for the image and all the time i was using it (and contributing). I'am also totally fine that you stopped maintaining it - it was free, so there is no obligations. I'am just thankful.

But not responding once, telling people that you decided to stop doing so (and even if it is for now) is just nothing i can respect. This is how you bring OSS down ... and after all you did to bring it up and maintaining it for years, this does the project no good.

Just state, as an disclaimer, that this image is for now no longer maintained and if you like and there is a fork that pushes it regularly, refer people (or not).

I did migrate to bitnami and i do not hold a grudge. It was a great time using this image, i'am thankful.

@EugenMayer
Copy link

EugenMayer commented Oct 22, 2024

In a more constructive manner:

For anybody else in need to migrate to bitnami (thanks @polarathene for providing the initial starter!) - those are the changes i found while migrating https://github.com/EugenMayer/docker-image-ldapexample to bitnami

  • when providing a boostrap.ldif, you will need to create the base yourself e.g
    dn: dc=example,dc=org
    dc: example
    objectClass: dcObject
    objectClass: organizationalUnit
    ou: Example Org
    
    bootstrap ldifs in general will work out of the box.
  • ldifs not longer support templating, so support for replacing {{ LDAP_BASE_DN }} in the ldis no longer exists
  • memberOf will need an schema, add this ldif to /schema/memberOf in the container
  • when activating TLS, you will need to generate the certificates yourself, if you want to have self-signed "test certs"
  • undocumented, but still existing in bitnami: LDAP_TLS_VERIFY_CLIENT: never
  • default ports are 1389 / 1636 (unprivileged) but can be changed via LDAP_PORT_NUMBER / LDAP_LDAPS_PORT_NUMBER
  • the bitnami container runs rootless/unprivileges (nice!) thus the default ports. Consider this, when mounting certs or similar (it runs under 1001:1001

I will port the helm chart https://github.com/EugenMayer/helm-openldap to bitnami too, this could take a while though.

@EugenMayer
Copy link

If anybody is interested, i adopted https://github.com/jp-gouin/helm-openldap which is already using bitnami/openldap and migrated from osixia. The way to migrate is currently summarized /designed in jp-gouin/helm-openldap#203 (that's the relevant part for here probably)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants