Fix deployment wizard to add the WAZUH_PROTOCOL variable only for UDP connections

[chantal-kelm]

Description

Now, the WAZUH_PROTOCOL variable is only displayed if a remote connection is of type secure and its protocol is UDP.

Notice

This issue was developed using Imposter, as we have not yet received a response from the @wazuh/framework team of a possible bug in the API. This issue must not be merged yet, as the code will be updated as soon as we have a reply from the @wazuh/framework team.

Issues Resolved

#4318

Evidence

Connection: Secure Protocol: UDP :

udpsecure.mp4

Connection: Secure Protocol: TCP :

TCPSECURE.mp4

Connection: Syslog

syslogtcpnosecure.mp4

Error handling and warning in the UI to the client.

error.mp4

Test

*Go to the Agents' tab
*Click on the 'Deploy new agent' button
*Verify that when a connection is type secure and its protocol is UDP, the variable WAZUH_PROTOCOL appears in the installation command, otherwise it does not appear.

You can use this data to test with the imposter:
CASE 1: Variable WAZUH_PROTOCOL should appear in the installation command.

{
    "data": {
      "remote": [
        {
          "connection": "syslog",
          "ipv6": "no",
          "protocol": [
            "UDP"
          ],
          "port": "514",
          "allowed-ips": [
            "0.0.0.0/0"
          ]
        },
        {
          "connection": "secure",
          "ipv6": "no",
          "protocol": [
            "UDP"
          ],
          "port": "1514",
          "queue_size": "131072"
        }
      ]
    },
    }, "error": 0
  }

Case 2: WAZUH_PROTOCOL variable should not appear in the install command

{
    "data": {
      "remote": [
        {
          "connection": "syslog",
          "ipv6": "no",
          "protocol": [
            "UDP"
          ],
          "port": "514",
          "allowed-ips": [
            "0.0.0.0/0"
          ]
        },
        {
          "connection": "secure",
          "ipv6": "no",
          "protocol": [
            "TCP"
          ],
          "port": "1514",
          "queue_size": "131072"
        }
      ]
    },
    }, "error": 0
  }

[Desvelao]

nitpick: If I am not wrong, this request gets the data of the master node. Related to this pull request #4737 that adds the selection of the manager to connect, the protocol should use the configurated by the selected manager.

For another hand, what should be the value of the protocol variable for the next situation (taking into account the mentioned pull request):

• manager1: tcp, udp
• manager2: udp

[Machi3mfl]

Added comment in the linked issue to tread this topic: #4318 (comment)

[yenienserrano]

CR: ☑️ with comments
Test: ✅

[Mayons95]

TR: ✔️
LGTM

Test details

[github-actions]

Code coverage (Jest)	%	values
Statements	8.09%	( 2966 / 36641 )
Branches	3.7%	( 1045 / 28214 )
Functions	7%	( 636 / 9080 )
Lines	8.15%	( 2858 / 35072 )

[AlexRuiz7]

Superseded by #4776