On Mon, Apr 11, 2011 at 4:39 PM, Justin Deoliveira wrote:
> Hi Victor,
>
> I believe this is a more specifically a geoserver issue... you should
> probably move the conversation there. As for the fix I still think modifying
> the SecuredObject* interfaces in geoserver to explicitly pass down the
>
Hi Victor,
I believe this is a more specifically a geoserver issue... you should
probably move the conversation there. As for the fix I still think modifying
the SecuredObject* interfaces in geoserver to explicitly pass down the
interface is the most robust option. But that is something for discus
Hi Andrea,
I am at a lost on how to resolve this issue as it only occurs on specific
environment. In our case its a debian server.
I believe it's some policy setting to created this issue but I do not know how
the policy works and I could not find any documentation on it as well. Would
you be
