[Security] Deprecate using UsageTrackingTokenStorage outside the request-response cycle #40785
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.
Currently, you get an "There is currently no session available" exception when using the
security.token_storage
service outside the main request-response cycle (e.g. in akernel.terminate
listener). This PR deprecates such usage and requires developers to update their definitions to explicitly usesecurity.untracked_token_storage
instead.A different solution would be to silently disable tracking in these cases, but I think that might create some unnecessary technical debt.