We are pleased to announce general availability of the Anaplan v2 Connector for MuleSoft. This new connector is based on Anaplan v2.0 APIs, with support for public key certificates.
New and updated features in the Anaplan v2 Connector for MuleSoft enable:
The Anaplan v2 Connector for MuleSoft enables customers to use public key certificates obtained from a Certificate Authority (CA) . You can purchase certificates from a CA that ends in a supported Root CA, then use your certificates for authentication with Anaplan. Authentication using CA certificates is considered a best practice in the industry, allowing you to leverage the benefits of a public key infrastructure.
Anaplan continues to support Anaplan Basic authentication, using a user ID and password.
The Anaplan v2 Connector for MuleSoft generates a token used in all subsequent API calls. The Anaplan v2 Connector for MuleSoft internally handles all steps necessary for authentication, including obtaining this token for API calls and refreshing expired tokens.
For more more information, see Administration: Certificates in Anapedia.
If you have to access Anaplan models across multiple tenants and want to run MuleSoft v2 integrations in these tenants, create different user IDs for different Tenants and use these user IDs to run your integrations.
The Anaplan v2 Connector for MuleSoft is based on Mule 3.8 runtime. The connector works on both Mule 3.8 and 3.9 runtimes. The Anaplan v2 Connector for MuleSoft is not supported on Mule 4.x runtimes due to changes in MuleSoft architecture. We plan to support the Mule 4.x runtime in a future release.
The Anaplan v2 Connector for MuleSoft replaces the v1 connector. Installations using the v1 connector will continue to work normally but the v1 connector will be deprecated and no longer available.