feat: HBMEIngestorService — Authelia SSO durch API-Key-Auth ersetzen #13
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/hbme-apikey-auth"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
X-API-KeyHeaderÄnderungen
modules/service_plugins/hbme_ingestor_service.py_load_config():username/password/auth_url→api_keystart(): kein CookieJar, keinauthenticate()-Aufrufsend_to_api():Cookie: authelia_session=...→X-API-Key: <key>test_connection(): Authelia-Zweischritt entfernt, direkt API-Key-Testget_stats():has_credentials/username/authenticated→has_api_keyauthenticate()und_extract_session_cookie()komplett entferntmodules/web_viewer/services_api.py_get_hbme_config(): gibthas_api_keystatthas_credentials/usernamezurück_save_hbme_config(): speichertapi_keystattusername/password/auth_url_toggle_hbme(): prüftapi_keystattusername+password_test_hbme(): kein Authelia-SSO-Schritt mehr_get_hbme_stats()(DB-Fallback):auth_url/username/passwordentferntconfigs/config.ini.exampleapi_urlaufhttp://localhost:8000/ingestor/packet(meshcore-ingestor Default)api_key-Option ergänztauth_urlundusername-Kommentar entferntTest plan
X-API-KeyHeader gesendettest_connection()funktioniert ohne SSO-Roundtrip🤖 Generated with Claude Code
MeshCore firmware supports three path hash sizes (1/2/3 bytes per node). Previously the bot always assumed 1-byte node hashes, silently misinterpreting paths when the device was configured for mode 1 or 2. Changes: - modules/core.py: Read path_hash_mode from self_info at connect time and store as bot.path_hash_mode (default 0 = 1-byte, unchanged behaviour) - modules/message_handler.py: - Add module-level helpers _path_bytes_to_nodes() and _path_hex_to_nodes() that chunk by configurable hash_size - decode_meshcore_packet(): pass device hash_size to _process_packet_path() - _process_packet_path(): accept hash_size parameter; TRACE path hashes remain 1-byte as per protocol spec - _update_mesh_graph_from_advert(): use device hash_size for node splitting - _store_observed_path(): use device hash_size for from_prefix/to_prefix - _format_path_string(): accept hash_size parameter - DM path display and _discover_message_path/_debug_decode_message_path: derive hash_size from contact's out_path_hash_mode field Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>