On Sat, Jan 24, 2015 at 1:51 PM, Niels Charlier <ni...@scitus.be> wrote:
> On 23-01-15 19:15, Andrea Aime wrote:
>
>> Either that, or you'll end up having to expand all possibilities and
>> maintain that expansion over time as layers
>> get added removed, with catalogs that have hundreds of thousands of items
>> it will simply become un-manageable,
>> meaning the security subsystem becomes suddenly unusable in those cases
>> (that we're pushing towards with
>> jdbcconfig, so it's not a made up use case...)
>>
>> Right.. that was my previous suggestion indeed, hence the different
> symbol for the 'expansion' wild card (versus a real wild card). Completely
> forget about this proposal. I've come up with a much better idea.
>
> I am convinced we can support all rules with wildcards followed by
> non-wildcards, whilst still keeping the hierarchical approach and minimal
> change to the implementation.
>
> All we need to do in order to keep the existing hierarchical approach is
> to maintain the rule that a non-wildcard at an earlier stage in the path
> ALWAYS takes preference, no matter the amount of wildcards.
On Sat, Jan 24, 2015 at 1:51 PM, Niels Charlier <ni...@scitus.be> wrote:
> All we need to do in order to keep the existing hierarchical approach is
> to maintain the rule that a non-wildcard at an earlier stage in the path
> ALWAYS takes preference, no matter the amount of wildcards. This means that
> workspace.layer.*.*
> takes preference over
> workspace.*.service.operation.
> even though the second rule looks more specific. Specificity earlier in
> the path wins.
>
I find it arbitrary and hard to understand/remember when faced with the
practical case,
say for example that I want to disable WFS for a workspace
topp.*.wfs.*.r=NO_ONE
then I want to add rules specific to a workspace because some layers are
private and
can only be seen by a certain user:
topp.states.r=ROLE_USA_CITIZEN
At this point I have to remember that this rule is actually re-enabling wfs
for topp.states
for that class of users, and add along a:
topp.states.wfs.*r=NO_ONE
to disable it also for topp;states.
I this is not confusing, then we don't have the same definition of the word
in mind...
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.
-------------------------------------------------------
------------------------------------------------------------------------------
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
