TUI authentication fix #604
Merged
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.
After implementing proper authentication between the backend, the client, and the web frontend, the TUI's previous authentication method was not considered, leading to it failing authentication when connecting to the backend server after the recent update.
This PR fixes that by adding an additional
elif ...block that takes the TUI's token into account and authorises that. In the longer term, having the TUI use the same authentication method as the instrument server would be ideal, but this is a lower priority.