Issue with AD server having LDAP Signing required

[krambos]

Server version: Ubuntu Server 24.04 LTS
Snipe-IT version: 7.1.15 - build 16052
Browser-specific issue: No

For compliance reasons, we had to enable the option "Require LDAP signing" on our Domain Controllers (Server 2022). This caused our Snipe-IT setup to break with the error "Could not bind to LDAP: Strong(er) authentication required". Is there any workaround or plan to support this kind of binding?

Note that the above is not the same as LDAPS (which you already support), but SASL.

[welcome]

👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can.

[uberbrady]

Is it possible that we already do support this, with our client-side certificates support? I've only ever seen that used with Google LDAP, but if it's the same protocol (and I think it's also SASL-based there), then it might work for you as well? Please do let us know, I'm really curious about that.

[krambos]

I can try, for sure. Which certs do I put there? I've never used Google LDAP.