-
Notifications
You must be signed in to change notification settings - Fork 317
Description
Checklist
- I have looked into the Readme, Examples, and FAQ and have not found a suitable solution or answer.
- I have looked into the API documentation and have not found a suitable solution or answer.
- I have searched the issues and have not found a suitable solution or answer.
- I have searched the Auth0 Community forums and have not found a suitable solution or answer.
- I agree to the terms within the Auth0 Code of Conduct.
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 of ManagementClient is typed as string, 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
| export interface ManagementClientOptionsWithToken extends ManagementClientOptions { | |
| token: string; | |
| } | |
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
const auth0ManagementClient = new ManagementClient({
token: () => Promise.resolve('my-token')
clientId,
domain,
audience,
scope,
});Alternatives and current workarounds
No response
Additional context
No response