Hello,
I have created a security zone which encompasses 1x remote gateway and when I change the security zones tag access from read, to read write, and read write edit, the rules seem to work just fine.
My next goal was to lock down the ability to write and edit tags from the gateway they are hosted on and only allow edits and writing from the remote gateway (aka the security zone). I went to the tag provider and pasted the security link, but this is not working. I am unable to edit or write to tags from the remote gateway anymore.
Any advice?
Reconsider your approach? The origin server for any tag is necessarily the master of it.
Is this why neither the security on the tag property nor the write permission on the tag provider do not work?
Do I need to create another security zone for the gateway the tag provider is hosted on and add it to the list, in order to make the remote tag writing from my desired security zone to work?
Yes, the remote gateway must itself be in a zone that is allowed to write into the tag provider--a zone defined on the origin server.
Copy, I believe this security is set up correctly, as seen in this image
My ultimate goal is to get it so a an approved role from this security zone can write to tags, but in trouble shooting I found the approved role worked, but once adding the security zone, I lost all functionality.
I know the security provider is set up correctly, because when I change permissions on the security zone i.e. read, read/write, read write edit, this changes what can be done from the remote gateway.
The trouble comes when I try to implement the security zone on a tag or tag provider, I loose all functionality from the remote gateway.
