feat: implement multiple token support and token management #1089
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.
Added new pages for join token management.
The token can be created, revoked and deleted.
Also support tokens with the expiration.
Introduced new resources:
JoinToken
- keeps the token, it's ID is the token string.JoinTokenStatus
- is generated by the controller, it calculates the information about the current token state: active, revoked or expired. And also has the information about if the token is default.DefaultJoinToken
- is the singleton resource that keeps the current default token id.The behavior of siderolink manager was changed to create a default
JoinToken
resource out of whatever is currently stored in thesiderolink.Config
resource.siderolink.ConnectionParams
is now generated by the controller. It's using the default token from theDefaultJoinToken
resource.Infra providers also rely on the default join tokens for now.
Fixes: #907