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
I'm trying to implement a process to call the Management API on AWS Lambda.
Since Lambda's execution environment scales horizontally, I want to cache the access token in SSM Parameter Store and share it across Lambda execution environments.
It seems that PR #793 allowed replacing the access token retrieval process with a custom-implemented function. I tried to implement a process using SSM Parameter Store utilizing this feature.
However, in the latest SDK version 4.11, the token constructor argument of ManagementClient is typed as string, making it impossible to replace it with a custom-implemented function.
Checklist
Describe the problem you'd like to have solved
I'm trying to implement a process to call the Management API on AWS Lambda.
Since Lambda's execution environment scales horizontally, I want to cache the access token in SSM Parameter Store and share it across Lambda execution environments.
It seems that PR #793 allowed replacing the access token retrieval process with a custom-implemented function. I tried to implement a process using SSM Parameter Store utilizing this feature.
However, in the latest SDK version 4.11, the
token
constructor argument ofManagementClient
is typed asstring
, making it impossible to replace it with a custom-implemented function.node-auth0/src/management/management-client-options.ts
Lines 8 to 11 in 9a5ca5c
I couldn't find the reason why the modification in #793 was reverted. Is it currently not possible to customize the access token retrieval process?
Describe the ideal solution
same as #793
Alternatives and current workarounds
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: