Changes to the policy exception in the CLI did not persist across ProxySG restart


Article ID: 168808


Updated On:


Asset Management Solution ProxySG Software - SGOS


After upgrading from SGOS 6.2 to 6.5, a change in exception from the CLI, such as creating a new exception or editing an existing exception, will cause the changes not to persist after a restart of the ProxySG.


In SGOS 6.2, by default the Text Editor contains the policy exceptions source. In SGOS 6.5 the default behavior is different: the Text Editor is empty and does not contain any policy exceptions source. If you make any changes in the Text Editor in 6.2, an upgrade to 6.5 will cause the ProxySG to migrate the changes done on the Text Editor as well. This means when you open up the Text Editor in 6.5 after the upgrade, it will no longer shows a blank or an empty Text Editor because it contains the changes that were done in 6.2.


This is an expected behavior or by design. Do not use the CLI to make the changes on the exception. You must use the ProxySG management console GUI or the Text Editor.