-
Notifications
You must be signed in to change notification settings - Fork 186
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added server address and wazuh protocol definition in Deploy agent section #5166
Added server address and wazuh protocol definition in Deploy agent section #5166
Conversation
This PR also resolves issue #5140 Now, when the Deploy Agent inputs changes don't launch new requests. Kazam_screencast_00000.mp4 |
public/controllers/agent/register-agent/steps/wz-manager-address.tsx
Outdated
Show resolved
Hide resolved
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
review:
code 🟢
Tests
Kibana 7.10.2
WIP
Legend:
⚫: none
🟢: passed
🔴: failed
🟡: warning
⚪: not applicable
UI
Test | Chrome | Firefox | Safari |
---|---|---|---|
For a manager master (cluster mode) configurated as TCP and UDP as the protocols of the remote secure connection, uses the TCP protocol. It should not display the WAZUH_PROTOCOL deployment variable | 🟢 | 🟢 | ⚫ |
For a manager master (cluster mode) configurated as TCP as the protocol of the remote secure connection, uses the TCP protocol. It should not display the WAZUH_PROTOCOL deployment variable | 🟢 | 🟢 | ⚫ |
For a manager master (cluster mode) configurated as UDP as the protocol of the remote secure connection, uses the UDP protocol. It should display the WAZUH_PROTOCOL deployment variable with UDP value | 🟢 | 🟢 | ⚫ |
For a manager master (manager mode) configurated as TCP and UDP as the protocols of the remote secure connection, uses the TCP protocol. It should not display the WAZUH_PROTOCOL deployment variable | 🟢 | 🟢 | ⚫ |
For a manager master (cluster mode) configurated as TCP as the protocol of the remote secure connection, uses the TCP protocol. It should not display the WAZUH_PROTOCOL deployment variable | 🟢 | 🟢 | ⚫ |
For a manager master (manager mode) configurated as UDP as the protocol of the remote secure connection, uses the UDP protocol. It should display the WAZUH_PROTOCOL deployment variable with UDP value | 🟢 | 🟢 | ⚫ |
Details
🟢 For a manager master (cluster mode) configurated as TCP and UDP as the protocols of the remote secure connection, uses the TCP protocol. It should not display the WAZUH_PROTOCOL deployment variable
Safari - ⚫
🟢 For a manager master (cluster mode) configurated as TCP as the protocol of the remote secure connection, uses the TCP protocol. It should not display the WAZUH_PROTOCOL deployment variable
Safari - ⚫
🟢 For a manager master (cluster mode) configurated as UDP as the protocol of the remote secure connection, uses the UDP protocol. It should display the WAZUH_PROTOCOL deployment variable with UDP value
Safari - ⚫
🟢 For a manager master (manager mode) configurated as TCP and UDP as the protocols of the remote secure connection, uses the TCP protocol. It should not display the WAZUH_PROTOCOL deployment variable
Safari - ⚫
🟢 For a manager master (cluster mode) configurated as TCP as the protocol of the remote secure connection, uses the TCP protocol. It should not display the WAZUH_PROTOCOL deployment variable
Safari - ⚫
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, @asteriscos. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-4.4-2.4-wzd 4.4-2.4-wzd
# Navigate to the new working tree
cd .worktrees/backport-4.4-2.4-wzd
# Create a new branch
git switch --create backport-5166-to-4.4-2.4-wzd
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 b167d6c4bc65b1b42029ddbab13c99c99cd43428
# Push it to GitHub
git push --set-upstream origin backport-5166-to-4.4-2.4-wzd
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-4.4-2.4-wzd Then, create a pull request where the |
…ction (#5166) * Added new WzServerAddressInput component * Updated CHANGELOG * Update state server address when is mounted * Resolved review comments * Updated CHANGELOG * Updated logic when protocol is UDP * Modified wazuh protocol param definition * Changed PR text in CHANGELOG * Reverted changes tsconfig (cherry picked from commit b167d6c)
…ction (#5166) * Added new WzServerAddressInput component * Updated CHANGELOG * Update state server address when is mounted * Resolved review comments * Updated CHANGELOG * Updated logic when protocol is UDP * Modified wazuh protocol param definition * Changed PR text in CHANGELOG * Reverted changes tsconfig (cherry picked from commit b167d6c)
…tion in Deploy agent section (#5173) Added server address and wazuh protocol definition in Deploy agent section (#5166) * Added new WzServerAddressInput component * Updated CHANGELOG * Update state server address when is mounted * Resolved review comments * Updated CHANGELOG * Updated logic when protocol is UDP * Modified wazuh protocol param definition * Changed PR text in CHANGELOG * Reverted changes tsconfig (cherry picked from commit b167d6c) Co-authored-by: Maximiliano Ibarra <6089438+Machi3mfl@users.noreply.github.com>
…n in Deploy agent section (#5172) Added server address and wazuh protocol definition in Deploy agent section (#5166) * Added new WzServerAddressInput component * Updated CHANGELOG * Update state server address when is mounted * Resolved review comments * Updated CHANGELOG * Updated logic when protocol is UDP * Modified wazuh protocol param definition * Changed PR text in CHANGELOG * Reverted changes tsconfig (cherry picked from commit b167d6c) Co-authored-by: Maximiliano Ibarra <6089438+Machi3mfl@users.noreply.github.com> Co-authored-by: Antonio <34042064+Desvelao@users.noreply.github.com> Co-authored-by: Federico Rodriguez <federico.rodriguez@wazuh.com>
Description
This PR, adds a new WzServerAddress component for the Deploy Agent section.
The component is a free input.
Closes #5138 #5140
Scope
Protocol cases
UDP
, theWAZUH_PROTOCOL
param in the command will showUDP
.TCP
, theWAZUH_PROTOCOL
param in the command will beTCP
(the param is hidden, and TCP is the default value)Server address input cases
enrollment.dns
field inManagement > Configuration
. The server address input must be filled by default with this value.Test cases evidence
Protocol cases
When the protocol is UDP (Cluster mode)
Management > Configuration > Global configuration > Remote Tab
UDP
Kazam_screencast_00005.mp4
When the protocol is TCP (
Cluster mode
)Management > Configuration > Global configuration > Remote Tab
Kazam_screencast_00006.mp4
When the protocol is UDP (
Manager mode
)Management > Configuration > Global configuration > Remote Tab
UDP
Kazam_screencast_00008.mp4
When the protocol is TCP (
Manager mode
)Management > Configuration > Global configuration > Remote Tab
Kazam_screencast_00007.mp4
Check List
yarn test:jest