Fix for using ExplicitMaxTTL in auth method plugins. #5379
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.
We like to use periodic tokens with explicit max TTL in one of our auth method plugins. The field logical.Auth.ExplicitMaxTTL was not serialized over proto bufs and in the token storage.
This PR fixes the serialization of ExplicitMaxTTL and enables to limit periodic tokens by setting the explicit max TTL in our plugins.