the reasoning is
1/ Redesigning security from start is an exercise that has already been
done. Geofence is a more advanced and flexible security system.
It would indeed make no sense to redesign the default security to bring
it to the same level.
2/ The design is therefore not completely reversed. There is full
backwards compatibility. Service and data security continues to exist.
There is only an optional added feature.
3/ The core idea was to expand on data security. Just as you can specify
per layer whether you can read and/or write to it, you can also specify
per layer which services can be used on it. The fact that it remains to
be primarily data security means that data and services are not treated
as orthogonal but services are considered a further specificity of the
rules here: in principle there is service security on a per layer basis.
(This compromise is a consequence of it being expansion rather than
redesign).
4/ Further to that, I proposed an increased flexibility in the use of
wildcards. It is possible to allow wildcards followed by non-wildcards
but continue the hierarchical implementation and semantics that exists
now. A wildcard means "everything that has not been specified in another
rule", but it must be read and interpreted from left to right with left
specificity having higher priority. This makes it possible to specify
service security on workspaces; in which case the wildcard in the layer
part means that that rule applies to all layers of the workspace for
which there is no specific rule.
Andrea objected mostly against point (4), although his argumentation
appeared to me to apply more against point (3).
Regards
Niels
On 28-01-15 09:25, Andrea Aime wrote:
On Wed, Jan 28, 2015 at 2:44 AM, Jody Garnett
<jgarn...@boundlessgeo.com <mailto:jgarn...@boundlessgeo.com>> wrote:
Thanks for the context Andrea.
So if I understand the proposal we are looking for a way to
reverse that design decision.
It looks that way, with the requirement that Niels added during the
conversation (control
services at the workspace level).
But if backwards compatibility is broken, we might as well fast track
a geofence integration,
as it would not be a slight chance, it would be a downright rewrite,
require a migration
path, and a rewrite of the docs (as such, something scheduled for
2.8.x only, Niels
insisting on the notion of "small changes" makes me think he's looking
for a solution
that could be backported, but maybe he just want one that requires
less work).
Cheers
Andrea
--
==
GeoServer Professional Services from the experts! Visit
http://goo.gl/NWWaa2 for more information.
==
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
*AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*
Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate.
Il loro utilizzo è consentito esclusivamente al destinatario del
messaggio, per le finalità indicate nel messaggio stesso. Qualora
riceviate questo messaggio senza esserne il destinatario, Vi preghiamo
cortesemente di darcene notizia via e-mail e di procedere alla
distruzione del messaggio stesso, cancellandolo dal Vostro sistema.
Conservare il messaggio stesso, divulgarlo anche in parte,
distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità
diverse, costituisce comportamento contrario ai principi dettati dal
D.Lgs. 196/2003.
The information in this message and/or attachments, is intended solely
for the attention and use of the named addressee(s) and may be
confidential or proprietary in nature or covered by the provisions of
privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New
Data Protection Code).Any use not in accord with its purpose, any
disclosure, reproduction, copying, distribution, or either
dissemination, either whole or partial, is strictly forbidden except
previous formal approval of the named addressee(s). If you are not the
intended recipient, please contact immediately the sender by
telephone, fax or e-mail and delete the information in this message
that has been received in error. The sender does not give any warranty
or accept liability as the content, accuracy or completeness of sent
messages and accepts no responsibility for changes made after they
were sent or for other risks which arise as a result of e-mail
transmission, viruses, etc.
-------------------------------------------------------
------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now.http://goparallel.sourceforge.net/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
