WebTop pecbridge update 5.4.5

[lucagasparini]

• Upgrade pecbridge 5.4.5 (download binary from Sonicle server with HTTP authentication)

• Changset list

• Add in config.xml variable for fromAddress

• Add in config.xml variable for notifyOwner (one of these 3 values ​​"all | auth | none")
  (eg: <sonicle-pec-bridge notifyOwner="auth" adminMail="lucag@neth.eu" fromAddress="pecbridge@neth.eu" port="10125">)

• all = all notifications sent to the pec owner

• auth = only notifications of failed authentication problems are sent to the pec owner

• none = no notifications are sent to the pec owner

All notifications are always sent to adminMail

Decide whether to also add changes on the webtop module UI to configure the two variables.

[gsanchietti]

Testing version: 1.4.0-testing.1

Test case 1: clean install

• On a new NethServer cluster, install a local user domain (OpenLDAP is good for this test) and a mail server
• Configure the mail server and associate it to the user domain
• Install WebTop: add-module ghcr.io/nethserver/webtop:1.4.0-testing.1
• Configure WebTop and connect it to the mail server
• Register the machine and enable the PEC bridge
• Verify the PEC bridge works correctly

Test case 2: update

• On a new NethServer cluster, install a local user domain (OpenLDAP is good for this test) and a mail server
• Configure the mail server and associate it to the user domain
• Install WebTop stable release from the Software Center
• Configure WebTop and connect it to the mail server
• Register the machine and enable the PEC bridge
• Verify the PEC bridge works correctly
• Update the webtop instance: api-cli run update-module --data '{"module_url": "ghcr.io/nethserver/webtop:1.4.0-testing.1", "instances": ["webtop1"]}'
• Verify the PEC bridge still works correctly

Test case 3: customization

• After test case 1 or 2
• Change the sender address and the notify action:

  runagent -m webtop1
  echo PECBRIDGE_FROM_ADDRESS=no-reply@test.org >> environment
  echo PECBRIDGE_NOTIFY_OWNER=auth >> environment
  

• Open the PEC bridge and force a synchronization
• Verify the new configurations are applied