With Machine-to-machine token, we need the ability to limit the scope issued in the token to be no more than what’s requested. I found this solution using custom hook: Client credentials request ignores scope parameter? However it looks like hooks are being deprecated. But when I try to do the sam…

Client credentials restrict scope with action instead of hook

jackie-linz September 21, 2023, 9:05pm 3

Thanks for the reply, but the document you linked is for user-login flow only.

The “api” object in machine to machine flow does not have an equivalent: Actions Triggers: credentials-exchange - API Object, and I get an error in the editor

1 Like

Topic		Replies	Views
Migrating M2M hook with custom response to actions Get Help custom-webtasks , deprecations	2	374	January 16, 2024
Assistance Needed: Modifying Access Token Scope in Machine to Machine Application Get Help management-api , actions-management-api	2	263	April 26, 2024
api.accessToken.addScope is not a function when used from onExecuteCredentialsExchange action template Get Help apis , application	5	113	October 1, 2024
Modify scope in post login action Get Help scopes , access-token , scope , actions-integrations	2	2776	January 8, 2024
Add custom parameter from request in access token through hooks in client credential flow Get Help auth0net , sdks-quickstarts	1	1188	January 8, 2024