[LDAP] Allow to use Nextclouds trusted certificate store for LDAPS
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
How to use GitHub
- Please use the 👍 reaction to show that you are interested into the same feature.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Is your feature request related to a problem? Please describe.
Currently, the LDAP module relies on certificates to be added to the system certificate store in /etc/ssl/certs in order to trust them. However especially in container deployments, it is not always possible to add custom certificates in there and rather hacky in the container world.
Describe the solution you'd like
It would be great if the LDAP module could additionally also trust the certificates that are added to the Nextcloud certificate store via occ security:certificates:import.
Describe alternatives you've considered
Maybe allow to configure LDAP_OPT_X_TLS_* in order to load the certificates from a different but writeable place?
Additional context
Currently, in AIO there are some workarounds but they are rather hacky.
Also see https://www.php.net/manual/en/ldap.constants.php#constant.ldap-opt-x-tls-cacertdir for the documentation for the ldap module.
cc @nextcloud/ldap
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in the LDAP module and trace how LDAPS currently uses the system certificate store at /etc/ssl/certs, then compare that with certificates imported through occ security:certificates:import. Done means LDAPS can trust certificates from Nextcloud's certificate store without requiring installation in the system store, including container deployments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- authentication
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100