mirror of
https://github.com/espressif/esp-rainmaker.git
synced 2026-01-14 11:24:14 +00:00
8ae0a34001
This feature is intended for mapping already-provisioned nodes to user accounts without re-provisioning. Common features (both implementations): - mDNS service: _esp_rmaker_chal_resp._tcp - TXT records: node_id, port, sec_version, pop_required - Optional instance name support (NULL uses node_id as default) - Supports Security 0, 1 (with/without PoP), and 2 (SRP6a) - Both use the same mDNS service type, simplifying CLI discovery 1. Standalone HTTP protocomm based challenge-response service. - Config: CONFIG_ESP_RMAKER_ON_NETWORK_CHAL_RESP_ENABLE - Endpoint: ch_resp (on protocomm HTTP server, default port 80) - Instance name via config.mdns_instance_name APIs: - esp_rmaker_on_network_chal_resp_start() - esp_rmaker_on_network_chal_resp_stop() - esp_rmaker_on_network_chal_resp_is_running() Note: Mutually exclusive with Local Control 2. Challenge-response support on local control. - Config: CONFIG_ESP_RMAKER_LOCAL_CTRL_CHAL_RESP_ENABLE - Endpoint: ch_resp (via esp_local_ctrl_set_handler) - Instance name via parameter to enable function APIs: - esp_rmaker_local_ctrl_enable_chal_resp(instance_name) - esp_rmaker_local_ctrl_disable_chal_resp() 3. CLI and console improvements. - CLI simplified to discover only _esp_rmaker_chal_resp._tcp service - Console command supports optional instance name: chal-resp-enable [instance_name] - Device discovery output shows instance name column Clients can choose to disable the challenge-response endpoint after usage to avoid potential misuse by other entities on the network. commit