'Collection is read-only' error after configuring layer security
Hi
I am in the throws of evaluating some of the enhancements available in GE 3.12, in particular the ability to define layer/component security.
However I don't seem to be able to get it to work where I have Group layers defined.
I have a couple of issues:
- Setting Deny permissions on the parent of the group has no effect on the child layers in that group if they are defined to Inherit permissions from the parent - their content is still visible in the Viewer. In fact, the Parent is still visible in the Viewer too, so it doesn't appear to do anything.
/customer/servlet/servlet.FileDownload?file=00P6000000e88OzEAI
- Leaving the parent to Inherit from a Site with Allow permissions, and setting all child layer permissions to Deny causes the initialization error 'Collection is read-only'. Leaving just one of those child layers to Inherit prevents the error, but then obviously that layer is visible in the Viewer. All other denied child layers are not, as I would expect.
/customer/servlet/servlet.FileDownload?file=00P6000000e88P4EAI
Anybody else experienced this issue or know how to prevent display of a Group layer and all children via Layer Security?
cheers
Ewan
PS I've done all the usual cache-clearing
-
I have seen the same behavior, I believe there is an issue with Group layer security Geocortex is working on.
I needed to un-group the layers I was working with, luckily there were only four so it was not as onerous as it could have been,
I have had success in denying access to map services, perhaps for now you could put those layers in a separate service, and set "allow" explicitly for the group you are granting access.
Eric
0 -
Hi Eric,
The 'Collection is read-only' error has been resolved and a fix will be in the next release.
--Ryan
0 -
Thanks for the info Ryan!
0 -
Wow! Nice to know Latitude are monitoring this forum so closely.
Thanks for the prompt replies from both of you.
I'll give the service separation idea a go in the meantime.
cheers
Ewan
0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
4 Kommentare