With the current implementation Connected Apps [Client Credentials] can only manage the Client Applications that it creates. Refer to this documentation: Creating Client Applications with Connected Apps.
In this article, we will discuss how to manage existing Client Applications using Connected Apps [Client Credentials].
After following these steps, you should not face the 403 Forbidden errors when trying to manage the specific, already-existing Client Application with a Connected App.
1) Retrieve the Organization ID as per this How to know my Organization ID (Org ID) on the Anypoint Platform
2) Retrieve the Org Admin token as per this How to generate your Authorization Bearer token for Anypoint Platform
3) Retrieve the Client Application info that is required to be managed by Connected App by executing the below API
https://anypoint.mulesoft.com/exchange/api/v1/organizations/{organization-id}/applications?query=&offset=0&limit=100
https://anypoint.mulesoft.com/apiplatform/repository/v2/organizations/{organization-id}/applications
4) Execute the below endpoint with the scope "manage:client_application" for each client application that is required to be managed by Connected Apps. Here the {connected-app-id} is the client ID of the connected application.
Note: This endpoint can only be executed by the user with the Org Admin role in the Master Org.
curl --location --request PATCH 'https://anypoint.mulesoft.com/accounts/api/connectedApplications/{connected-app-id}/scopes' \
--header 'Authorization: Bearer {Organization Admin token}' \
--header 'Content-Type: application/json' \
--data '{"scopes":[
{
"scope": "manage:client_application",
"context_params": {
"org": "{organization-id}",
"applicationId": "{client-application-id}",
"clientId": "{client-application-client-id}"
}
}
]
}'
Note: Connected Apps have limits on the number of apps per user, per organization and also each Connected App can have a limit of scopes. Adding the manage:client_application scope is counted toward this limit.
For more information on the limits, please refer to our documentation.
001116119

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.