Porting and Chaining
Local Edition Porting
You can port this connector to a customer-specific bundle in the Local Edition.
Cloud API Management can port this connector for a specific Local Edition customer. For assistance with porting or chaining connectors, contact Boomi Support via Boomi Community.
Local Edition Chaining
OAuth2JWT natively supports chaining and can be chained with existing processors (Connectors) API Management developed and available. e.g. If you want to chain API Allowlisting Connector with OAuth2JWT connector you can do something like below. (Sample only)
Processing
-
Processing adapter: com.mashery.proxy.customer.generic.oauth2-jwt-authenticator
-
Perform pre-processing: Enabled
-
Data to make available for pre-processing (one per line) sample/example.
-
processors:com.mashery.proxy.customer.generic.white-listing-connector
-
com.mashery.proxy.customer.generic.white-listing-connector.HeaderParams:{"RatePlan": "PQRST"}
-
jwks_cache_expiry:5
-
jwks_uri: http://mashery-jwk-test.public-dev.acme.com/jwks.json
-
Do not chain Oauth2JWT: com.mashery.proxy.customer.generic.oauth2-shared-token-adapter, as both OAuth2JWT authenticator and OAuth2 Shared token adapter are chained adapters and will not work after chaining. The functionality of OAuth2 Shared token adapter is integrated into OAuth2JWT authenticator and just provide the preinput parameter: shared\_token\_spkey:<SPKey of another API service.
