Configuring a Mule Cloud Account
- Karl Henselin
- Chandresh Patel
Many plugin operations require the FDMULE_CLOUD_ACCOUNT_CODEtarget property to be set. See Configuring Cloud Accounts for more info. The following properties are required for the Mule Cloud Account.
Property Name | Property Code | Required | Description |
|---|---|---|---|
Anypoint URL |
| Yes | URL of the Anypoint environment. e.g. https://anypoint.mulesoft.com |
Auth Type |
| Yes |
|
Organization Name |
| Yes | Mule Organization Name |
Environment Name |
| Yes | Mule Environment Name |
Username |
| For Basic Auth | The username for Authenticating with Anypoint. Used for Basic Auth only. |
Password |
| For Basic Auth | The password for Used for Basic Auth only. |
Client Id |
| For OAuth | The client id for Authenticating with Anypoint. Used for OAuth only. |
Client Secret |
| For OAuth | The secret for Used for OAuth only. |
Creating a Client Id and Secret for Mule OAuth
Mule Cloud Accounts can be setup for Basic Auth or OAuth. For OAuth, this document will assist you in preparing to connect.
As an administrator, log into your Anypoint account.
Go to connected apps (e.g. https://anypoint.mulesoft.com/accounts/connectedApps)
Click Create App.
Give it a Name.
Choose Client Credentials.
Click Add Scopes.
There are a lot of scopes, and a lot of plugin operations and ways that the plugin can be used. Choose the scopes that you need for what you want to do. Mule has pretty good explanations of what each does. If you miss a scope, you will get a 403 running the operation, and you can come back at any time and add more. If you add environments or organizations (business groups) later, you will likely need to come back and add them also. Here are some scopes that you will need for most scenarios.
Area | Scope |
|---|---|
General | View Environment View Organization |
API Manager
| Application Creator Application Viewer Deploy API Proxies |
Runtime Manager | Create Applications Delete Applications Read Applications Read Servers
|
Choose all the relevant business groups and environments. It is recommended to have 2 clients, one for NonProdFlexDeploy and one for FlexDeploy. The non-prod FlexDeploy application that you made should not have permissions to the higher environments, as it is only for testing.
Click Next.
Click Save.
Use the Copy Id and Copy Secret buttons to copy the client id and client secret which you will paste into FlexDeploy in the Integrations → Cloud section.
Related content
- style