Re: [Geoserver-users] ldap security issues in 2.16/17

: [Geoserver-users] ldap security issues in 2.16/17 Not, when Geoserver and the ldap service are in the same private network. Or? Stefan Am 01.06.2020 um 23:40 schrieb Humphries, Graham: > As I understand it not using TLS in your LDAP configuration means your > authentication details are

Re: [Geoserver-users] ldap security issues in 2.16/17

On 6/2/20 8:15 AM, Stefan Overkamp wrote: > Not, when Geoserver and the ldap service are in the same private > network. Or? Yes this is a private Windows Office environment (and not LDAP, but an Active Directory server). Not sure what the standard is in the AD world. I'm just an user of a

Re: [Geoserver-users] ldap security issues in 2.16/17

security problem. > > -Original Message- > From: Stefan Overkamp [mailto:overk...@posteo.de] > Sent: Tuesday, 2 June 2020 1:34 AM > To: rdmaili...@duif.net > Cc: GeoServer Mailing List List > Subject: Re: [Geoserver-users] ldap security issues in 2.16/17 > &g

Re: [Geoserver-users] ldap security issues in 2.16/17

...@duif.net Cc: GeoServer Mailing List List Subject: Re: [Geoserver-users] ldap security issues in 2.16/17 Hi Richard, we are using LDAP. LDAp was already running fine 2 years ago with Geoserver 2.13 when I joined my new employer. Our role service confguration (german ui) is approximately as follows

Re: [Geoserver-users] ldap security issues in 2.16/17

Hi Richard, we are using LDAP. LDAp was already running fine 2 years ago with Geoserver 2.13 when I joined my new employer. Our role service confguration (german ui) is approximately as follows: Administrator Role: ROLE_ADMIN Group administrator role: ROLE_GRUPPEN_ADMIN Server-URL:

Re: [Geoserver-users] ldap security issues in 2.16/17

Hi Stefan, Thank, for the check! I was eager to see if it fitted, but we already did not configure TLS ... I tested both, but without success Are you authenticating against an Active Directory, or ldap? Pretty frustrating this. There is so much to configure with magic terms like (member={0}) etc

Re: [Geoserver-users] ldap security issues in 2.16/17

Hi list, we are running geoserver 2.17.0 in a docker container with tomcat:9.0.31-jdk11-openjdk and have no problems. I took a look into our ticket system and found an issue 2 month ago with ldap I had to change geoserver/security/role/[ourroleservicename]/config.xml from |true | to |false |

Re: [Geoserver-users] ldap security issues in 2.16/17

On 5/29/20 7:01 PM, Andrea Aime wrote: > On Fri, May 29, 2020 at 2:56 PM Richard Duivenvoorde > mailto:rdmaili...@duif.net>> wrote: > > Anybody a clue? Only thing that changes is java (and I cannot test that > because 2.13 does not work with java11, and 2.16 not with java8 (mmm > THAT

Re: [Geoserver-users] ldap security issues in 2.16/17

On Fri, May 29, 2020 at 2:56 PM Richard Duivenvoorde wrote: > Anybody a clue? Only thing that changes is java (and I cannot test that > because 2.13 does not work with java11, and 2.16 not with java8 (mmm > THAT I did test). > Mind, in my company we run 2.16.x and 2.17.x with Java 8

Re: [Geoserver-users] ldap security issues in 2.16/17

I'd suggest running 2.16 or 2.17 with Java 8 - to rule out a java change. If it continues to be an issue then we'll need to look to see if there were any changes in the LDAP authentication code. Ian On Fri, 29 May 2020 at 13:51, Richard Duivenvoorde wrote: > Hi List, > > We have/had a working

[Geoserver-users] ldap security issues in 2.16/17

Hi List, We have/had a working setup to secure layers based on LDAP/AD groups. All works fine in 2.13.1 java8 (Windows machines, all java from adoptopenjdk) Then we got a new server (Windows0) and installed 2.16 (also tried 2.17) and jdk11 and with identical setup I NEVER receive my 'groups'...