On 3/30/22 06:54, Brad Hards wrote:
Possibly no-one uses LDAP in the same way you do. Maybe they do, but didn't upgrade yet. Possibly they didn't notice the problem.
Well I can second Alexander at least. We have for some layers an old Geoserver version running, which works for us to authenticate against Windows AD, which broke at a sudden version and never could get it to work anymore. I'll try Stefan's fix, but if I'm correct we tried that already. I'll be on that premise next Tuesday to try (again?). These AD setups are tricky because it is hard to create a reproducible failing test for it. The AD setups of the average Windows environments are often a hell/mess, and never 'open'. I even looked to ask for a dump of the AD and checked if I could maybe put it somewhere on a public cloud (but AD is not 'free' etc etc, the dump contains too much info etc etc) So: Acme example is doing fine indeed. But @Brad also take people who have a (frustrating) issue serious, it is often not so easy to create a reproducible issue... What I did: mailed with the dev who did the ldap-group thingie, and asked for a quote. But this could very much be 'configuration/environment' issue. A solution would maybe be to have even more fine-grained debug info? Regards, Richard Duivenvoorde _______________________________________________ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
