Enhanced Security Measures in Place: To ensure a safer experience, we’ve implemented additional, temporary security measures for all users.
06-07-2021 07:20 AM
Hi - I create a service (tcp-443) and then create a security rule that uses this service as the service member.
This works.
Then, if I call the same API call with the same xpath and provide a different service, say tcp-449, the resulting security rule has *both* tcp-443 and tcp-449 in the Service column:
First call is <service>["tcp-443"]</service>
Second call is <service>["tcp-449"]</service>
xpath: `/config/devices/entry[@name='localhost.localdomain']/device-group/entry[@name='${ deviceGroup }']/${ rulebase }/security/rules/entry[@name='${ entryName }']`
I would like the second call to replace "tcp-443" with "tcp-449" - what it is doing is appending "tcp-449" to the services. Can I do that without deleting the security rule and re-adding it?
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!
