Re: [Geoserver-devel] proposal: LDAP UserGroupService

Hi Niels The jdbc implementation uses a propterty file for all sql statements ./main/resources/org/geoserver/security/jdbc/usersdml.xml Do you plan something similar to the ldap implementation. The nice thing is that users can adjust the queries to their environment. Cheers On Mon, May 2,

[Geoserver-devel] Reminder: GeoTools / GeoServer Meeting at 19:30 UTC on Tuesday

GeoTools / GeoServer committee meeting on Skype at 19:30 UTC on Tuesday: http://www.timeanddate.com/worldclock/fixedtime.html?msg=GeoTools+%2F+GeoServer+Meeting=2016=5=3=19=30=0=1 -- Ben Caradoc-Davies Director Transient Software Limited New Zealand

[Geoserver-devel] Jenkins build is back to normal : geoserver-2.9.x #4

See -- Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple

Re: [Geoserver-devel] Fix for GeoServer 2.9.x nightly build

Thanks for fixing that Alessandro, I must have missed that when I was copying the builds over. Torben On Mon, May 2, 2016 at 3:55 AM, Alessandro Parma < alessandro.pa...@geo-solutions.it> wrote: > Dear All > > Just wanted to report a minor change I made to the build job on >

[Geoserver-devel] Build failed in Jenkins: geoserver-2.9.x #3

See -- [...truncated 2830 lines...] [INFO] [INFO]

Re: [Geoserver-devel] Hazelcast/JDBConfig clustering issues caused by HTTP 302 response and unique wicket resource IDs

So as suspected this is a consequence of wicket7 upgrade. The generated id preserves the state of the page and prevents the "double submit problem" to occur. The feature can be turned off with a simple setting to make it clustering compatible. However that will imply that refreshing a page

Re: [Geoserver-devel] proposal: LDAP UserGroupService

Thanks, Simone. Extra information: It would be implemented in an analogue way to the RoleService. The different method implementations would execute LDAP search queries to retrieve the requested user information and translate the data to user/group objects. Configuration would also be similar

Re: [Geoserver-devel] proposal: LDAP UserGroupService

Ciao Christian, I did not know that :) Regards, Simone Giannecchini == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Ing. Simone Giannecchini @simogeo Founder/Director GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy

Re: [Geoserver-devel] proposal: LDAP UserGroupService

Hi @Simone, GeoServer uses caching already. Its the same as if you are using a user group store based on JDBC. No need to implement a special LDAP cache for serving requests. Cheers On Mon, May 2, 2016 at 4:53 PM, Chris Snider wrote: > Hi, > > I tried the link below

[Geoserver-devel] Jenkins build is back to normal : 2.9-cite-wms-1.3 #4

See -- Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple

[Geoserver-devel] Jenkins build is back to normal : 2.9-cite-wcs-1.1 #4

See -- Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple

[Geoserver-devel] Jenkins build is back to normal : 2.9-cite-wms-1.1 #4

See -- Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple

[Geoserver-devel] Jenkins build is back to normal : 2.9-cite-wfs-1.0 #4

See -- Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple

Re: [Geoserver-devel] proposal: LDAP UserGroupService

Hi, I tried the link below and it wound up on a "Create new wiki" page. Removing the -- at the end resulted in https://github.com/geoserver/geoserver/wiki/GSIP-144 This page did open. Chris Snider Senior Software Engineer Intelligent Software Solutions, Inc. -Original Message-

Re: [Geoserver-devel] proposal: LDAP UserGroupService

+1 The proposal is not _tremendously_ detailed but I think this is a feature that is needed. If you can just elaborate a little on the proposal itself that would be great. As an instance, do you intend to put same caching in between GS and LDAP to avoid LDAP sloweness slowing down request

[Geoserver-devel] Jenkins build is back to normal : 2.9-cite-wcs-1.0 #4

See -- Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple

[Geoserver-devel] Fix for GeoServer 2.9.x nightly build

Dear All Just wanted to report a minor change I made to the build job on http://ares.boundlessgeo.com/jenkins/ I noticed a bug in the nightly build for GeoServer 2.9.x this morning. The "Branch Specifier" in the build was set correctly to 2.9.x but the "ver" environment variable in the build

Re: [Geoserver-devel] proposal: LDAP UserGroupService

Added my +1 Cheers On Mon, May 2, 2016 at 10:46 AM, Niels Charlier wrote: > Hello, > > I was waiting to make this proposal for after the release: > > https://github.com/geoserver/geoserver/wiki/GSIP-144-- > > Basically: There is no LDAP UserGroupService yet. Some people might

[Geoserver-devel] proposal: LDAP UserGroupService

Hello, I was waiting to make this proposal for after the release: https://github.com/geoserver/geoserver/wiki/GSIP-144-- Basically: There is no LDAP UserGroupService yet. Some people might want one. For example, to use the integrated geofence with ldap, because the integrated geofence relies

[Geoserver-devel] Jenkins build is back to normal : geoserver-master-nightly #1015

See -- Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance

[Geoserver-devel] Build failed in Jenkins: 2.9-cite-wms-1.3 #3

See -- [...truncated 960 lines...] + (( i++ )) + (( i <= 100 )) + sleep 2 + echo 'Pinging GeoServer at http://localhost:11010/geoserver' Pinging GeoServer at http://localhost:11010/geoserver +

[Geoserver-devel] Build failed in Jenkins: 2.9-cite-wcs-1.1 #3

See -- [...truncated 963 lines...] + (( i++ )) + (( i <= 100 )) + sleep 2 + echo 'Pinging GeoServer at http://localhost:11010/geoserver' Pinging GeoServer at http://localhost:11010/geoserver +

[Geoserver-devel] Build failed in Jenkins: 2.9-cite-wms-1.1 #3

See -- [...truncated 960 lines...] + (( i++ )) + (( i <= 100 )) + sleep 2 + echo 'Pinging GeoServer at http://localhost:11010/geoserver' Pinging GeoServer at http://localhost:11010/geoserver +

[Geoserver-devel] Build failed in Jenkins: 2.9-cite-wfs-1.0 #3

See -- [...truncated 1062 lines...] + (( i++ )) + (( i <= 100 )) + sleep 2 + echo 'Pinging GeoServer at http://localhost:11010/geoserver' Pinging GeoServer at http://localhost:11010/geoserver +

[Geoserver-devel] Build failed in Jenkins: 2.9-cite-wcs-1.0 #3

See -- [...truncated 966 lines...] + (( i++ )) + (( i <= 100 )) + sleep 2 + echo 'Pinging GeoServer at http://localhost:11010/geoserver' Pinging GeoServer at http://localhost:11010/geoserver +