Skip to content

Conversation

@tomponline
Copy link
Member

When using a certificate add token stored in an operation on a non-local cluster member the expiry time of the token wasn't being taken into account due to incorrect data type conversion and error checking.

@tomponline tomponline requested a review from markylaing July 12, 2024 08:03
@tomponline tomponline self-assigned this Jul 12, 2024
Copy link
Contributor

@markylaing markylaing left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM just a couple of comments to update :)

 - An expired token could be used if operation was non-local due to missing validation & conversion.
 - Use happy path code style.
 - Explicitly check operation's location in order to decide unmarshalling format of `request` field rather than rely on errors - allows for better validation.

Signed-off-by: Thomas Parrott <[email protected]>
…ion in test_clustering_trust_add

Signed-off-by: Thomas Parrott <[email protected]>
@tomponline tomponline merged commit ca61dee into canonical:main Jul 12, 2024
@tomponline tomponline deleted the tp-token-expiry branch July 12, 2024 08:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants