Set Up

Version	Min runtime version	Compatible Java versions	Description
https://central.sonatype.com/artifact/io.github.mulesoft-forge/mule-idp-connector/1.0.3	4.6.X	Java 17, Java 11, Java 8	Java 17 support
https://central.sonatype.com/artifact/io.github.mulesoft-forge/mule-idp-connector/1.0.2	4.6.X	Java 11, Java 8	Proxy support Bug Fix - Action and Version drop-downs load all
https://central.sonatype.com/artifact/io.github.mulesoft-forge/mule-idp-connector/1.0.1	4.6.X	Java 11, Java 8	Deprecated Utils PDFBox
https://central.sonatype.com/artifact/io.github.mulesoft-forge/mule-idp-connector/1.0.0	4.6.x	Java 11, Java 8	Launch

Serving Open Source Components Since 2002 The Central Repository is the largest collection of Java and other open source components. It provides the easiest way to access and distribute your software components to millions of developers.

Step1: Maven Central Repository

Edit Project File pom.xml

The MuleSoft Forge connectors are constantly updated, and the version is regularly changed. Make sure to replace {version} with the latest release from Maven Central.

Copy and paste the following Maven Dependency into your Mule application pom file.

pom.xml

<dependency>
    <groupId>io.github.mulesoft-forge</groupId>
    <artifactId>mule-idp-connector</artifactId>
    <version>{version}</version>
    <classifier>mule-plugin</classifier>
</dependency>

• See Anypoint Code Builder Example: Note xml <dependencies> tags if not present.

  

Step2: Access Management

To access the following operations:

1. Service IDP - Execution - Submit

2. Service IDP - Execution Result - Retrieve

Create a Connected App with the following details:

• Type: App acts on its own behalf (client credentials)

• Scopes: Execute Published Actions

After you create the connected app, copy its ID and Secret for Connector Configuration.

---

To access platform API you need to supply Anypoint User Account details with the following User details:

• Multi-factor auth: Exempted

• Permissions: Document Actions - Manage Actions

Step3: Test API

Learn API first at speed outside of MuleSoft - Postman

If you are unfamiliar with the underlying API to a connector and not sure you have permissions right please fight those issues in Postman/SoapUI first.

Here is a complete Postman Collection:

595KB

MuleSoft IDP Universal 🌐 REST Smart Connector 🔌.postman_collection.json

Step4: Connector Configuration

Anypoint Studio

1

⚙️ Create Global Element Connector Configuration

• Choose Global Type, restricting on "idp"

  

2

⚙️ Default Config Settings

• MuleSoft IDP Config default settings are as follows:

  

3

⚙️ Enter your Settings

Tip - Enter OAuth first as the configuration UI validates that first

OAuth 3️⃣

• Client id: ID of the connected app to call IDP

• Client secret: Secret of the connected app to call IDP

• Token url: URL to obtain the access token for your connected app

  Default: https://anypoint.mulesoft.com/accounts/api/v2/oauth2/token

• Scopes: Leave Empty

Example Completed Region:

IDP API 1️⃣

• MuleSoft IDP Service Host: Select your IDP service host. The drop down values are the currently supported regions

• MuleSoft Organization Id: Enter your MuleSoft Organization Id (Org Id) that your MuleSoft IDP entitlement exists https://help.salesforce.com/s/articleView?id=001115130&type=1

Example Completed Region:

Platform API 2️⃣

Mulesoft Account for Config Introspection and Platform API

Optional but if you want to have dynamic drop downs when configuring your operations at design time and or you want to call a Platform API operation it becomes mandatory

Introspection for what IDP document actions are published and what versions at Design Time!

• MuleSoft Platform Account Host: Select your Anypoint region host. The drop down values are the most frequently set but feel free to enter manually your region such as Hyperforce

• MuleSoft Platform Account Username: MuleSoft login user name
• MuleSoft Platform Account Password: MuleSoft login password

Example Completed Region:

ObjectStore 4️⃣

The IDP obtained access tokens are stored in an ObjectStore. By default, the SDK will store them in the apps’s default store, but users can define their own custom one

Example Completed Region:

4

✅ Test Connection

Of course you can use Configuring Properties - Property Placeholders

Anypoint Code Builder

1

⚙️ Create Global Element Connector Configuration

• Currently ACB does not have a dedicated Global Configuration Elements UI, so create the configuration as part of the configuration of the first IDP Operation configuration of the project

  

2

⚙️ Enter your Settings

OAuth 3️⃣

• Client id: ID of the connected app to call IDP

• Client secret: Secret of the connected app to call IDP

• Token url: URL to obtain the access token for your connected app

  Default: https://anypoint.mulesoft.com/accounts/api/v2/oauth2/token

• Scopes: Leave Empty

Example Completed Region:

IDP API 1️⃣

• Name: Enter MuleSoft_IDP_Config

• Connection: Leave as Connection

• MuleSoft IDP Service Host:

  • Press the Blue Refresh Icon (Value Provider)

  • The drop down values are the currently supported regions

  

  • MuleSoft Organization Id: Enter your MuleSoft Organization Id (Org Id) that your MuleSoft IDP entitlement exists https://help.salesforce.com/s/articleView?id=001115130&type=1

Example Completed Region:

Platform API 2️⃣

MuleSoft Account for Config Introspection and Platform API

Optional but if you want to have dynamic drop downs when configuring your operations at design time and or you want to call a Platform API operation it becomes mandatory

Introspection for what IDP document actions are published and what versions at Design Time!

• MuleSoft Platform Account Host: Select your Anypoint region host. The drop down values are the most frequently set but feel free to enter manually your region such as Hyperforce

• MuleSoft Platform Account Username: MuleSoft login user name
• MuleSoft Platform Account Password: MuleSoft login password

Example Completed Region:

ObjectStore 4️⃣

The IDP obtained access tokens are stored in an ObjectStore. By default, the SDK will store them in the apps’s default store, but users can define their own custom one

Completed Region:

3

✅ Test Connection