Did you raise an issue about this so that the developers would see it?

LDAP tends not to be something any one (I know) plays with in their spare
time so you might also want to raise it with a commercial support supplier.

Ian

On Thu, 31 Mar 2022 at 11:37, Brandon M <johndeere...@gmail.com> wrote:

> Hi,
>
> I ran into this same problem last year when we upgraded GeoServer from
> 2.12.2 to 2.19.2.  Here's the thread I opened on the issue back then:
>
>
> https://sourceforge.net/p/geoserver/mailman/geoserver-users/thread/CA%2B8gfLZ_55Vi%3Ds65PynNh34ScUFc4aJjFWFuXYFdQbP%2BqBFBXg%40mail.gmail.com/#msg37271563
>
> Our discussions didn't produce any results, so I ended up going with
> this hack after we upgraded to GeoServer 2.19.2, removed these two
> jars:
> gs-sec-ldap-2.19.2.jar
> gs-web-sec-ldap-2.19.2.jar
>
> Then installing the related jars from the last working version, 2.15.2:
> gs-sec-ldap-2.15.2.jar
> gs-web-sec-ldap-2.15.2.jar
>
> This got things working for our use and hasn't caused any issues.
>
> FYI, there was another person in our same boat:
>
>
> https://sourceforge.net/p/geoserver/mailman/geoserver-users/thread/d2bb87fd-7a89-0aa5-7a3f-e975aaeba967%40posteo.de/
>
> Thanks,
> Brandon
>
>
>
> On Wed, Mar 30, 2022 at 5:58 PM Brad Hards <br...@frogmouth.net> wrote:
> >
> > On Wednesday, 30 March 2022 10:29:35 PM AEDT you wrote:
> > > Indeed, I only need to bind the user to check the user identity, which
> will
> > > always be considered as an administrator of GeoServer. If we need to
> have a
> > > dedicated group into LDAP to do so, I will see if it is possible.
> >
> > If you enable the "Bind user before searching for groups" checkbox, it
> looks
> > like the provided user (i.e. whoever is logging in) will be used for the
> bind
> > operation. So you don't need to provide the credentials in the
> authentication
> > configuration for that case.
> >
> > I didn't actually try it, but there is a test that verifies the
> behaviour.
> >
> > Brad
> >
> >
> >
> >
> >
> > _______________________________________________
> > 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
>
>
> _______________________________________________
> 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
>


-- 
Ian Turton
_______________________________________________
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

Reply via email to