[OGUI-1710] Handle newly generated token from central system#2992
Merged
[OGUI-1710] Handle newly generated token from central system#2992
Conversation
…sending connections in ConnectionManager
…liceO2Group/WebUi into feature/TKN/OGUI-1703/basic-typescript-interfaces
…liceO2Group/WebUi into feature/TKN/OGUI-1703/basic-typescript-interfaces
…ithub.com:AliceO2Group/WebUi into feature/TKN/OGUI-1704/data-serialization-utils
…ub.com:AliceO2Group/WebUi into feature/TKN/OGUI-1705/client-central-basic-stream
OmegaCreations
changed the title
…OGUI-1710/handle-newly-generated-token
…on inside of them
graduta
approved these changes
Nov 13, 2025
graduta
deleted the
feature/TKN/OGUI-1710/handle-newly-generated-token
branch
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.
I have JIRA issue created
In the scope of this PR I have created new command for token creation. For now,
ConnectionDirection.DUPLEXis handled like two different Connection instances for Sending and Receiving. If there will be a need for duplex connection we can change that. I believe there is no need for that, besides the one we have for CentralConnection.