Closed
Description
Hi team,
As part of wazuh/wazuh#10399 new options have been added to the Registration Service configuration. Here you can see the API response when adding the new key_request
block.
# curl -k -X GET "https://localhost:55000/agents/000/config/auth/auth" -H "Authorization: Bearer $TOKEN"
{
"data": {
"auth": {
"port": 1515,
"disabled": "no",
"remote_enrollment": "yes",
"use_source_ip": "no",
"purge": "yes",
"use_password": "no",
"ssl_verify_host": "no",
"ssl_auto_negotiate": "no",
"ciphers": "HIGH:!ADH:!EXP:!MD5:!RC4:!3DES:!CAMELLIA:@STRENGTH",
"ssl_manager_cert": "etc/sslmanager.cert",
"ssl_manager_key": "etc/sslmanager.key",
"key_request": {
"enabled": "yes",
"exec_path": "python3 /root/key_request_db.py",
"socket":"/tmp/key_request_socket",
"timeout": 60,
"threads": 1,
"queue_size": 1024
},
"force": {
"enabled": "yes",
"key_mismatch": "yes",
"disconnected_time": {
"enabled": "no",
"value": 3600
}
}
}
},
"error": 0
}
The goal of this issue is to be able to see the new block key_request
and its options inside the Registration Service
section. This block is optional so it can be missing in the API response.
Best regards.