You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As the cache of the Management API's token is local to the execution process we end-up generating a lot of Machine-to-Machine tokens when scaling our application horizontally. Having a way to decentralised the cache would help us to reduce the number of generated tokens.
Describe the ideal solution
Ideally we could pass a method to the token properties to handle ourselves the caching mechanism:
adamjmcgrath
added
the
enhancement
An enhancement or improvement to the SDK that could not be otherwise categorized as a new feature
label
Mar 14, 2023
Describe the problem you'd like to have solved
As the cache of the Management API's token is local to the execution process we end-up generating a lot of Machine-to-Machine tokens when scaling our application horizontally. Having a way to decentralised the cache would help us to reduce the number of generated tokens.
Describe the ideal solution
Ideally we could pass a method to the
token
properties to handle ourselves the caching mechanism:We can also imagine leveraging on the existing Automatic Management API Token Retrieval features:
Alternatives and current work-arounds
Currently the only solution I see is to create multiple instance of the ManagementClient to control which token is passed to it.
Additional information, if any
The text was updated successfully, but these errors were encountered: