Require authenticated webhook delivery and document n8n setup - #3
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Webhook delivery now requires a Bearer token stored with Android Keystore encryption. Queued requests retain their original encrypted token and destination; legacy requests without authentication are blocked. All DevServer scenarios use provisioned n8n Header Auth credentials.
Includes the bilingual n8n and Telegram guides from #2, updated for authenticated setup, plus privacy documentation.
Validation: 35 Android tests, debug/release lint and builds, Python tests/style, live n8n authentication smoke tests, and emulator delivery of test events, notifications and SMS after process restart.