[Geoserver-devel] GSIP 182 - Show a tab and table of roles for each layer, layer group, workspace

GeoServer GeoServer Developer
1

Dear all,

I would like to submit to your attention the following geoserver improvement proposal:

https://github.com/geoserver/geoserver/wiki/GSIP-182.

Best regards,
Marco Volpini

2

I like the idea, care should be taken in the description as this is not the only security consideration in play when trying to access a layer.

Thoughts for discussion:

  • Consider moving to a security heading on the Data tab to be clear it is about the raw data itself… not sure I like it.
  • Not all the data restrictions are defined layer-by-layer, how do you wish to show the workspace restrictions? “tiger.*” in your example? One though would be to add a similar tab to the workspace screen, …
  • To communicate workspace restrictions a text description of the workspace restrictions could be provided below the proposed roles table
  • This may also be a good though to provide a summary of the service restrictions in play for the layer?
  • A better thought would be to show the workspace restrictions in the same roles table, but grayed out and not editable …
  • Do we need to consider the tileset permissions separately?

Putting the above together:
a) add “name” column to the roles table so both “tiger.*” and “tiger.tiger_roads” are listed
b) workspace rows are grayed out, only used to communicate data access restrictions already in place
c) consider adding a similar tab to the workspace screen if you want to go for consistency

···

–
Jody Garnett

3

Hi Jody,
thank you for the feedback, please check my replies bellow:

I like the idea, care should be taken in the description as this is not the only security consideration in play when trying to access a layer.

Thoughts for discussion:

  • Consider moving to a security heading on the Data tab to be clear it is about the raw data itself… not sure I like it.

I’m -1 on this one :(, that say, not sure what you mean by raw data, let’s see what others thing.

This new tab allows to manage the security of the layer, read or write, I can see in the future to grow to allow other modules to contribute.
The data tab already seems a bit crowded to me.

  • Not all the data restrictions are defined layer-by-layer, how do you wish to show the workspace restrictions? “tiger.*” in your example? One though would be to add a similar tab to the workspace screen, …

Yes a tab will be added on workspaces allowing to:

  • configuring workspaces admin
  • and read write permission for the workspace
  • To communicate workspace restrictions a text description of the workspace restrictions could be provided below the proposed roles table
  • This may also be a good though to provide a summary of the service restrictions in play for the layer?
  • A better thought would be to show the workspace restrictions in the same roles table, but grayed out and not editable …
  • Do we need to consider the tileset permissions separately?

I see the four last points as interesting new functionalities, but they are out of scope of this proposal.
Allowing to configure the roles associated and permissions of a layer directly on the layer configuration page, seems to me that it is already a significant and self contained functionality :slight_smile:

···

Regards,
Nuno Oliveira

GeoServer Professional Services from the experts!
Visit http://goo.gl/it488V for more information.

Nuno Miguel Carvalho Oliveira
@nmcoliveira
Software Engineer

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

Con riferimento alla normativa sul trattamento dei dati
personali (Reg. UE 2016/679 - Regolamento generale sulla
protezione dei dati “GDPR”), si precisa che ogni
circostanza inerente alla presente email (il suo contenuto,
gli eventuali allegati, etc.) è un dato la cui conoscenza
è riservata al/i solo/i destinatario/i indicati dallo
scrivente. Se il messaggio Le è giunto per errore, è
tenuta/o a cancellarlo, ogni altra operazione è illecita.
Le sarei comunque grato se potesse darmene notizia.

This email is intended only for the person or entity to
which it is addressed and may contain information that
is privileged, confidential or otherwise protected from
disclosure. We remind that - as provided by European
Regulation 2016/679 “GDPR” - copying, dissemination or
use of this e-mail or the information herein by anyone
other than the intended recipient is prohibited. If you
have received this email by mistake, please notify
us immediately by telephone or e-mail.

4

Dear all,
this proposal has been around for almost 20 days, and no votes have been cast :-)

Is there anything we can do to make the proposal more clear or friendly?
I discussed this functionality with a few users and they seem to think it is a good addition.

So feel free to shoot your opinions or votes.

@Jody let me know if I answer your comments.

Thank you!

On Sun, 2019-10-20 at 18:09 +0100, Nuno Oliveira GeoSolutions wrote:

Hi Jody,
thank you for the feedback, please check my replies bellow:

On Wed, Oct 16, 2019 at 11:44 PM Jody Garnett <jody.garnett@anonymised.com> wrote:

I like the idea, care should be taken in the description as this is not the only security consideration in play when trying to access a layer.

Thoughts for discussion:

  • Consider moving to a security heading on the Data tab to be clear it is about the raw data itself… not sure I like it.

I’m -1 on this one :(, that say, not sure what you mean by raw data, let’s see what others thing.

This new tab allows to manage the security of the layer, read or write, I can see in the future to grow to allow other modules to contribute.
The data tab already seems a bit crowded to me.

  • Not all the data restrictions are defined layer-by-layer, how do you wish to show the workspace restrictions? “tiger.*” in your example? One though would be to add a similar tab to the workspace screen, …

Yes a tab will be added on workspaces allowing to:

  • configuring workspaces admin
  • and read write permission for the workspace
  • To communicate workspace restrictions a text description of the workspace restrictions could be provided below the proposed roles table
  • This may also be a good though to provide a summary of the service restrictions in play for the layer?
  • A better thought would be to show the workspace restrictions in the same roles table, but grayed out and not editable …
  • Do we need to consider the tileset permissions separately?

I see the four last points as interesting new functionalities, but they are out of scope of this proposal.
Allowing to configure the roles associated and permissions of a layer directly on the layer configuration page, seems to me that it is already a significant and self contained functionality :slight_smile:

Putting the above together:
a) add “name” column to the roles table so both “tiger.*” and “tiger.tiger_roads” are listed
b) workspace rows are grayed out, only used to communicate data access restrictions already in place
c) consider adding a similar tab to the workspace screen if you want to go for consistency

–
Jody Garnett

On Thu, 10 Oct 2019 at 02:26, marco.volpini@anonymised.com8… <marco.volpini@anonymised.com> wrote:

Dear all,

I would like to submit to your attention the following geoserver improvement proposal:

https://github.com/geoserver/geoserver/wiki/GSIP-182.

Best regards,
Marco Volpini

Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

_______________________________________________
Geoserver-devel mailing list
[Geoserver-devel@anonymised.comsts.sourceforge.net](mailto:Geoserver-devel@lists.sourceforge.net)
[https://lists.sourceforge.net/lists/listinfo/geoserver-devel](https://lists.sourceforge.net/lists/listinfo/geoserver-devel)


-- 
Regards,
Nuno Oliveira
==
GeoServer Professional Services from the
experts! 
Visit http://goo.gl/it488V for more information.
==

Nuno Miguel Carvalho Oliveira
@nmcoliveira
Software Engineer

GeoSolutions S.A.S.
Via di Montramito 3/A
55054  Massarosa (LU)
Italy
phone: +39 0584 962313
fax:      +39 0584 1660272

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

-------------------------------------------------------

Con riferimento alla normativa sul trattamento dei dati 
personali (Reg. UE 2016/679 - Regolamento generale sulla 
protezione dei dati “GDPR”), si precisa che ogni 
circostanza inerente alla presente email (il suo contenuto, 
gli eventuali allegati, etc.) è un dato la cui conoscenza 
è riservata al/i solo/i destinatario/i indicati dallo 
scrivente. Se il messaggio Le è giunto per errore, è 
tenuta/o a cancellarlo, ogni altra operazione è illecita. 
Le sarei comunque grato se potesse darmene notizia.

This email is intended only for the person or entity to 
which it is addressed and may contain information that 
is privileged, confidential or otherwise protected from 
disclosure. We remind that - as provided by European 
Regulation 2016/679 “GDPR” - copying, dissemination or 
use of this e-mail or the information herein by anyone 
other than the intended recipient is prohibited. If you 
have received this email by mistake, please notify 
us immediately by telephone or e-mail.
5

Looks good to me, I assume the tab defaults to allow all being on?

+1

Ian

(attachments)

face-smile.png

···

Ian Turton

6

+1

(attachments)

face-smile.png

···

Regards,
Simone Giannecchini

GeoServer Professional Services from the experts!
Visit http://bit.ly/gs-services for more information.

Ing. Simone Giannecchini
@simogeo
Founder/Director

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 333 8128928

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia.

This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.

7

Hi Nuno,
just read the proposal. I’m generally good with ut, but the module capabilities bit worries me, it seems
the design only considered GeoFence as a possible ResourceAccessManager alternative.
In fact, there is plenty of ResourceAccessManager around (it’s one of the bits we customize the most in
custom setups), but the code, as written, will keep on displaying the tabs even if the they can’t be used, unless
those modules are upgraded to expose the right module metadata (most of the time, they don’t have a module
metadata at all).

The security subsystem in SecureCatalogImpl works by looking in the classpath for a ResourceAccessManager
implementation, and if one is found, then it’s used, otherwise the default one is used:
https://github.com/geoserver/geoserver/blob/e0771561a5e131f33387b0a0197b3c7bb577848f/src/main/src/main/java/org/geoserver/security/SecureCatalogImpl.java#L103

Given the new UI makes sense only if the DefaultResourceAccessManager is used, I’d suggest
a simpler alternative: ask SecureCatalogImpl what it is using (there is only one SecureCatalogImpl in the classpath).

Now, the ResourceAccessManager used is already available via a getter, but it can be wrapped, and the wrapper
interface is not unwrapping friendly. Options:

  • Add a simple boolean field “usingDefaultAccessManager” in SecureCatalogImpl that would be set while creating the DefaultResourceAccessManager, and a getter to get it
  • Or if you prefer, make the resorce access manager wrappers unwrapping friendly, and if you get a wrapper back from the catalog, query it and check if it’s wrapping a DefaultResourceAccessManager. See also the java.sql.Wrapper class.

I’m also going to have a look at the PR and add extra feedback there.

Cheers

Andrea

···

Regards, Andrea Aime == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it ------------------------------------------------------- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.

8

Hi,
after checking the code I’ve realized that there is another important issue to be considered: who can edit the rules?
Right now, only a full admin can edit security access rules, as that page is not visible to workspace admins… but they
can see the layers, so this GSIP actually makes workspace admins able to edit security rules, while before they could
have not.
I would make the tabs visible only to a full admin by default, and if you really need it to be available to workspace admins
too, I’d suggest to add a configuration to enable/disable it (defaulting to disabled, to avoid security breaches on upgrades).

Also, looking at the UI and code, it seems that “admin” rights can be set on layers and layer groups… but I believe this
is misleading, admin level access are performed only on workspaces, in the UI and REST API, if memory serves me right…
the documentation still has a note about it:
https://docs.geoserver.org/stable/en/user/security/layer.html#access-modes

I suggest to check if this is still the case, and if so, don’t offer admin rights in the UI for layers and groups… that said, the current
UI allows to setup admin rights on layers… I believe due to the GUI being dumb… of well, not a big deal in the end, it’s misleading
but “documented”, see what you want to do about it (eventually nothing).

Cheers
Andrea

···

Regards, Andrea Aime == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it ------------------------------------------------------- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.

9

Hello Andrea,
thanks for your review, pr contains now your feedbacks.

Il giorno gio 31 ott 2019 alle ore 18:16 Andrea Aime <andrea.aime@anonymised.com> ha scritto:

Hi,
after checking the code I’ve realized that there is another important issue to be considered: who can edit the rules?
Right now, only a full admin can edit security access rules, as that page is not visible to workspace admins… but they
can see the layers, so this GSIP actually makes workspace admins able to edit security rules, while before they could
have not.
I would make the tabs visible only to a full admin by default, and if you really need it to be available to workspace admins
too, I’d suggest to add a configuration to enable/disable it (defaulting to disabled, to avoid security breaches on upgrades).

Also, looking at the UI and code, it seems that “admin” rights can be set on layers and layer groups… but I believe this
is misleading, admin level access are performed only on workspaces, in the UI and REST API, if memory serves me right…
the documentation still has a note about it:
https://docs.geoserver.org/stable/en/user/security/layer.html#access-modes

I suggest to check if this is still the case, and if so, don’t offer admin rights in the UI for layers and groups… that said, the current
UI allows to setup admin rights on layers… I believe due to the GUI being dumb… of well, not a big deal in the end, it’s misleading
but “documented”, see what you want to do about it (eventually nothing).

Cheers
Andrea

On Thu, Oct 31, 2019 at 4:55 PM Andrea Aime <andrea.aime@anonymised.com8…> wrote:

Hi Nuno,
just read the proposal. I’m generally good with ut, but the module capabilities bit worries me, it seems
the design only considered GeoFence as a possible ResourceAccessManager alternative.
In fact, there is plenty of ResourceAccessManager around (it’s one of the bits we customize the most in
custom setups), but the code, as written, will keep on displaying the tabs even if the they can’t be used, unless
those modules are upgraded to expose the right module metadata (most of the time, they don’t have a module
metadata at all).

The security subsystem in SecureCatalogImpl works by looking in the classpath for a ResourceAccessManager
implementation, and if one is found, then it’s used, otherwise the default one is used:
https://github.com/geoserver/geoserver/blob/e0771561a5e131f33387b0a0197b3c7bb577848f/src/main/src/main/java/org/geoserver/security/SecureCatalogImpl.java#L103

Given the new UI makes sense only if the DefaultResourceAccessManager is used, I’d suggest
a simpler alternative: ask SecureCatalogImpl what it is using (there is only one SecureCatalogImpl in the classpath).

Now, the ResourceAccessManager used is already available via a getter, but it can be wrapped, and the wrapper
interface is not unwrapping friendly. Options:

  • Add a simple boolean field “usingDefaultAccessManager” in SecureCatalogImpl that would be set while creating the DefaultResourceAccessManager, and a getter to get it
  • Or if you prefer, make the resorce access manager wrappers unwrapping friendly, and if you get a wrapper back from the catalog, query it and check if it’s wrapping a DefaultResourceAccessManager. See also the java.sql.Wrapper class.

I’m also going to have a look at the PR and add extra feedback there.

Cheers

Andrea

On Thu, Oct 10, 2019 at 11:36 AM marco.volpini@anonymised.com <marco.volpini@anonymised.com> wrote:

Dear all,

I would like to submit to your attention the following geoserver improvement proposal:

https://github.com/geoserver/geoserver/wiki/GSIP-182.

Best regards,
Marco Volpini

Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

–

Regards, Andrea Aime == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it ------------------------------------------------------- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.

–

Regards, Andrea Aime == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it ------------------------------------------------------- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.

10

Thank you Marco, then happy to vote with a +1

Cheers
Andrea

···

Regards, Andrea Aime == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it ------------------------------------------------------- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.

11

+0

On Wed, 2019-10-30 at 10:09 +0000, Nuno Oliveira wrote:

Dear all,
this proposal has been around for almost 20 days, and no votes have been cast :-)

Is there anything we can do to make the proposal more clear or friendly?
I discussed this functionality with a few users and they seem to think it is a good addition.

So feel free to shoot your opinions or votes.

@Jody let me know if I answer your comments.

Thank you!

On Sun, 2019-10-20 at 18:09 +0100, Nuno Oliveira GeoSolutions wrote:

Hi Jody,
thank you for the feedback, please check my replies bellow:

On Wed, Oct 16, 2019 at 11:44 PM Jody Garnett <jody.garnett@anonymised.com> wrote:

I like the idea, care should be taken in the description as this is not the only security consideration in play when trying to access a layer.

Thoughts for discussion:

  • Consider moving to a security heading on the Data tab to be clear it is about the raw data itself… not sure I like it.

I’m -1 on this one :(, that say, not sure what you mean by raw data, let’s see what others thing.

This new tab allows to manage the security of the layer, read or write, I can see in the future to grow to allow other modules to contribute.
The data tab already seems a bit crowded to me.

  • Not all the data restrictions are defined layer-by-layer, how do you wish to show the workspace restrictions? “tiger.*” in your example? One though would be to add a similar tab to the workspace screen, …

Yes a tab will be added on workspaces allowing to:

  • configuring workspaces admin
  • and read write permission for the workspace
  • To communicate workspace restrictions a text description of the workspace restrictions could be provided below the proposed roles table
  • This may also be a good though to provide a summary of the service restrictions in play for the layer?
  • A better thought would be to show the workspace restrictions in the same roles table, but grayed out and not editable …
  • Do we need to consider the tileset permissions separately?

I see the four last points as interesting new functionalities, but they are out of scope of this proposal.
Allowing to configure the roles associated and permissions of a layer directly on the layer configuration page, seems to me that it is already a significant and self contained functionality :slight_smile:

Putting the above together:
a) add “name” column to the roles table so both “tiger.*” and “tiger.tiger_roads” are listed
b) workspace rows are grayed out, only used to communicate data access restrictions already in place
c) consider adding a similar tab to the workspace screen if you want to go for consistency

–
Jody Garnett

On Thu, 10 Oct 2019 at 02:26, marco.volpini@anonymised.com <marco.volpini@anonymised.com> wrote:

Dear all,

I would like to submit to your attention the following geoserver improvement proposal:

https://github.com/geoserver/geoserver/wiki/GSIP-182.

Best regards,
Marco Volpini

Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

_______________________________________________
Geoserver-devel mailing list
[Geoserver-devel@anonymised.comsts.sourceforge.net](mailto:Geoserver-devel@lists.sourceforge.net)
[https://lists.sourceforge.net/lists/listinfo/geoserver-devel](https://lists.sourceforge.net/lists/listinfo/geoserver-devel)


-- 
Regards,
Nuno Oliveira
==
GeoServer Professional Services from the
experts! 
Visit http://goo.gl/it488V for more information.
==

Nuno Miguel Carvalho Oliveira
@nmcoliveira
Software Engineer

GeoSolutions S.A.S.
Via di Montramito 3/A
55054  Massarosa (LU)
Italy
phone: +39 0584 962313
fax:      +39 0584 1660272

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

-------------------------------------------------------

Con riferimento alla normativa sul trattamento dei dati 
personali (Reg. UE 2016/679 - Regolamento generale sulla 
protezione dei dati “GDPR”), si precisa che ogni 
circostanza inerente alla presente email (il suo contenuto, 
gli eventuali allegati, etc.) è un dato la cui conoscenza 
è riservata al/i solo/i destinatario/i indicati dallo 
scrivente. Se il messaggio Le è giunto per errore, è 
tenuta/o a cancellarlo, ogni altra operazione è illecita. 
Le sarei comunque grato se potesse darmene notizia.

This email is intended only for the person or entity to 
which it is addressed and may contain information that 
is privileged, confidential or otherwise protected from 
disclosure. We remind that - as provided by European 
Regulation 2016/679 “GDPR” - copying, dissemination or 
use of this e-mail or the information herein by anyone 
other than the intended recipient is prohibited. If you 
have received this email by mistake, please notify 
us immediately by telephone or e-mail.

_______________________________________________
Geoserver-devel mailing list
[Geoserver-devel@anonymised.comsts.sourceforge.net](mailto:Geoserver-devel@lists.sourceforge.net)
[https://lists.sourceforge.net/lists/listinfo/geoserver-devel](https://lists.sourceforge.net/lists/listinfo/geoserver-devel)


-- 
Regards,
Nuno Oliveira
==
GeoServer Professional Services from the
experts! 
Visit http://goo.gl/it488V for more information.
==

Nuno Miguel Carvalho Oliveira
@nmcoliveira
Software Engineer

GeoSolutions S.A.S.
Via di Montramito 3/A
55054  Massarosa (LU)
Italy
phone: +39 0584 962313
fax:      +39 0584 1660272

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

-------------------------------------------------------

Con riferimento alla normativa sul trattamento dei dati 
personali (Reg. UE 2016/679 - Regolamento generale sulla 
protezione dei dati “GDPR”), si precisa che ogni 
circostanza inerente alla presente email (il suo contenuto, 
gli eventuali allegati, etc.) è un dato la cui conoscenza 
è riservata al/i solo/i destinatario/i indicati dallo 
scrivente. Se il messaggio Le è giunto per errore, è 
tenuta/o a cancellarlo, ogni altra operazione è illecita. 
Le sarei comunque grato se potesse darmene notizia.

This email is intended only for the person or entity to 
which it is addressed and may contain information that 
is privileged, confidential or otherwise protected from 
disclosure. We remind that - as provided by European 
Regulation 2016/679 “GDPR” - copying, dissemination or 
use of this e-mail or the information herein by anyone 
other than the intended recipient is prohibited. If you 
have received this email by mistake, please notify 
us immediately by telephone or e-mail.
12

Hi guys, my +1

···

==

GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information.

Ing. Alessio Fabiani

@alfa7691
Founder/Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A - 55054 Massarosa (LU) - Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 331 6233686

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia.

This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.

13

+0

···

Regards,
Simone Giannecchini

GeoServer Professional Services from the experts!
Visit http://bit.ly/gs-services for more information.

Ing. Simone Giannecchini
@simogeo
Founder/Director

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 333 8128928

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia.

This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.

14

As per our voting rules:
https://docs.geoserver.org/latest/en/developer/policies/gsip.html#voting-on-a-gsip

… looks like this proposal has been accepted.

The associated pull request will be merged shortly:
https://github.com/geoserver/geoserver/pull/3809

Thank you all for the discussion,
Nuno Oliveira

On Thu, 2019-10-10 at 11:25 +0200, marco.volpini@anonymised.com wrote:

Dear all,

I would like to submit to your attention the following geoserver improvement proposal:

https://github.com/geoserver/geoserver/wiki/GSIP-182.

Best regards,
Marco Volpini

_______________________________________________
Geoserver-devel mailing list
[Geoserver-devel@anonymised.comsts.sourceforge.net](mailto:Geoserver-devel@lists.sourceforge.net)
[https://lists.sourceforge.net/lists/listinfo/geoserver-devel](https://lists.sourceforge.net/lists/listinfo/geoserver-devel)


-- 
Regards,
Nuno Oliveira
==
GeoServer Professional Services from the
experts! 
Visit http://goo.gl/it488V for more information.
==

Nuno Miguel Carvalho Oliveira
@nmcoliveira
Software Engineer

GeoSolutions S.A.S.
Via di Montramito 3/A
55054  Massarosa (LU)
Italy
phone: +39 0584 962313
fax:      +39 0584 1660272

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

-------------------------------------------------------

Con riferimento alla normativa sul trattamento dei dati 
personali (Reg. UE 2016/679 - Regolamento generale sulla 
protezione dei dati “GDPR”), si precisa che ogni 
circostanza inerente alla presente email (il suo contenuto, 
gli eventuali allegati, etc.) è un dato la cui conoscenza 
è riservata al/i solo/i destinatario/i indicati dallo 
scrivente. Se il messaggio Le è giunto per errore, è 
tenuta/o a cancellarlo, ogni altra operazione è illecita. 
Le sarei comunque grato se potesse darmene notizia.

This email is intended only for the person or entity to 
which it is addressed and may contain information that 
is privileged, confidential or otherwise protected from 
disclosure. We remind that - as provided by European 
Regulation 2016/679 “GDPR” - copying, dissemination or 
use of this e-mail or the information herein by anyone 
other than the intended recipient is prohibited. If you 
have received this email by mistake, please notify 
us immediately by telephone or e-mail.