feat: Add support for bearer tokens#661
Open
knolleary wants to merge 1 commit into
Open
Conversation
knolleary
changed the title
hardillb
approved these changes
Jun 23, 2026
hardillb
left a comment
hardillb
left a comment
Contributor
There was a problem hiding this comment.
I thought I remembered doing a bunch of this before....
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
2 participants
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.
This is the final part of FlowFuse/flowfuse#6594 - enabling HTTP Bearer token support to remote instances.
The code here is identical to that used by hosted instances.
I have tested against FlowFuse/flowfuse#7579 (branch:
7566-device-token-ui) - note it requires setting Device Agent version to 4.0.0 in its package.json. I've held off including that change in this PR to not confuse matters.