This Issue adressed the sync problem for IBM-Bluepages-LDAP-Servers. However this isn’t a generic fix.
My university has a OpenLDAP-Server, which has the same problem, that only a handfull of users are synced. However it works when using the “force_no_page” param.
I propose a dropdown to configure this option when adding a new LDAP-connection. I already implemented the change in this fork.
I’m completely new to ruby and coffee-script so I’d like some feedback
I have a screenrecording of the working feature but cannot append it to this post. You can watch it here.
I still have the old workaround in the code. Removing it would mean all IBM-Bluepages-Users need to add a new connection with this new Property.
I’m running a Zammad instance as well running into the same problem.
Currently, I have to comment out code (" if @host == ‘bluepages.ibm.com’ ") manually, which is obviously a “dirty hack” for a certain known issue that IBM seemed to recognize first as the comment above this code states: special workaround for IBM bluepages see issue #1422 for more details
As this is now obviously a problem that other LDAP instances experiance as well, the proposed solution to add this to the regular configuration options in the GUI are absolutely reasonable!
Actually, in my case it is in fact an MS Active Directory which Zammad is configured to access via the LDAP protocol.
It may be that @LuckyLuisHD only referred to it as “OpenLDAP”-Server not knowing that the LDAP protocol used can also be served by an Active Directory server.
It is an issue that can occur with different LDAP backends, the Zammad code mentions this for IBM, the gem docs for MSAD (s.a.) and we do in fact have an issue fixed by the no_page option with openLDAP (reproduces in our setup).
yes I also read the docs and don’t know why it works, I just tried different options and this worked. I don’t have precise information about what OpenLDAP-Server is used by my university. I will ask my admin and post the information here as soon as I have it.
I contacted my admins. We use a OpenLDAP Version 2.5.13 Server with Debian Bookworm.
@YetAnotherGerrit I think the issues above show that there is a need for this option with several types of LDAP-Installations.
Do you guys have any feedback about my proposed implementation?
Are there maybe more NET:LDAP-Connection-Parameters that should be configureable for the user? What I found is that the other parameters aren’t as important as the force_no_page. @casus 's proposal a few years ago sould support more params, but i think a button like i propose looks better.
Do you have any opionions on the need of other configuration options from the gem’s docs?
do you have any opinions on how I can continue on this issue?
I think the addition of this feature is reasonable, since there have been multiple cases now, where people couldn’t properly use the LDAP-Integration without this parameter.
I can create a PR, so the specific changes I wrote can be discussed. If you want to handle this issue in another way, please let me know.
