Hi Zdenek,
Thanks for looking into this issue and offering to test it out. I've
asked our LDAP administrator for the ldif file for our system, I'll
let you know if he can provide that to me. If you don't mind
providing me with your test steps, that would be great, I would like
to double check
Hi Richard,
Hi Brandon,
I have recently tested ApacheDS with Geoserver main branch and I got roles
working without problems. I have done a quick test in 2.15.2 to be sure my
use case works there too.
Do you think it will be good enough to test with ApacheDS studio?
FYI: I'm in the same boat:
see:
https://sourceforge.net/p/geoserver/mailman/geoserver-users/thread/d2bb87fd-7a89-0aa5-7a3f-e975aaeba967%40posteo.de/
My gutfeeling is that 'something' (recursive groups?) were added which break
old setups.
We have not been able to make this work in newer
Hi Stefan,
Thanks for getting back to me on this issue. I see you are using a
slightly different approach with
https://docs.geoserver.org/latest/en/user/security/usergrouprole/roleservices.html
than what I've configured.
I have been using the LDAP authentication provider which is documented
Hi,
in my configuration I have additional:
cn=*
(defaults to cn=*) and
cn=huhu,dc=geodaten,dc=de
GANZGEHEIM
Also, see
https://docs.geoserver.org/latest/en/user/security/usergrouprole/roleservices.html
Groups are extracted from a specific LDAP node, configured as
the |Groups search base|.
Hi GeoServer Users,
We recently upgraded to a new version of GeoServer, 2.16.2 from 2.12.2
(I know we are a little behind the curve). We have GeoServer
configured to use our internal LDAP for user login, and assign users
GeoServer ADMIN privileges based on their LDAP groups, which is
configured
