| Re: [geomesa-users] [External] Re: [geomesa-dev] GeoMesa Accumulo Custom Iterator |
|
Hi Meet,
I believe the docs are correct - if you look at SecurityUtils, it is just doing the same thing as the "or, equivalently" line:
https://github.com/locationtech/geomesa/blob/main/geomesa-security/src/main/java/org/locationtech/geomesa/security/SecurityUtils.java#L33
In the first feature-level example, we are also setting the visibility as an attribute, so that it can be visualized in geoserver. The visibility is not returned as part of a WFS/WMS response, so we add it as an attribute instead. However, the attribute shouldn't affect the visibility handling at all, it is purely for visualization.
But it sounds like you got things working now? Great to hear!
Thanks,
Emilio Lahr-Vivaz
General Atomics, CCRi
From: Patel, Meet RTX <meet.2.patel@xxxxxxx>
Sent: Monday, July 15, 2024 9:31 AM To: jnhuva@xxxxxxxxx <jnhuva@xxxxxxxxx>; Lahr-Vivaz, Emilio <Emilio.Lahr-Vivaz@xxxxxxxxxxx> Subject: RE: [External] Re: [geomesa-users] [geomesa-dev] GeoMesa Accumulo Custom Iterator Jim, Emilio,
I tried getting the attribute level visibility to work multiple times before considering support of implementation. After looking at the feature level visibility tutorial https://www.geomesa.org/documentation/stable/tutorials/geomesa-examples-featurelevelvis.html . I noticed that both lines
// set the visibility as user data in the feature SecurityUtils.setFeatureVisibility(feature, visibilities); // also set as an attribute for visualization feature.setAttribute("visibility", visibilities);
are needed whereas the attribute level documentation https://www.geomesa.org/documentation/stable/user/datastores/security.html states to have either the first line OR equivalently the second line.
SecurityUtils.setFeatureVisibility(feature, "admin,user,admin,user") // or, equivalently: feature.getUserData().put("geomesa.feature.visibility", "admin,user,admin,user");
I believe that there is a documentation error which initially caused me to not get the attribute level visibility to work. Removing the “//or, equivalently:” comment would be great as both lines are needed to get the visibilities to work.
Let me know if this is a real find.
Thanks, Meet
From: geomesa-users <geomesa-users-bounces@xxxxxxxxxxx>
On Behalf Of James Hughes via geomesa-users
Hi Meet,
Are you trying to implement feature or attribute level visibility? If you are trying to filter entire records, then it is feature level and things are way easier!
Either way, have you gone through the feature level visibility tutorial here: https://www.geomesa.org/documentation/stable/tutorials/geomesa-examples-featurelevelvis.html ?
Even if you are working on attribute level vis, you'll want to run through that tutorial and some of the others here: https://github.com/geomesa/geomesa-tutorials/tree/main/geomesa-tutorials-accumulo.
Emilio's suggestion is an outline of how to implement things yourself. That is a decent bit of work; hopefully the existing functionality will let you get things going!
Cheers,
Jim
On Tue, Jul 2, 2024 at 3:58 PM Lahr-Vivaz, Emilio via geomesa-dev <geomesa-dev@xxxxxxxxxxx> wrote:
|