Support for multiple user roles in Integration flows sender Adapters (HTTP, SOAP, REST, ODATA etc)

[vinaymittal]

Hello Everyone,

I have a scenario where I have two packages PackageA and PackageB both packages contain Synchronous iflows with HTTP Sender adapter,

PackageA iflows are accessible only via custom role PackageAMessaging.send 

and 

PackageB iflows are accessible only via custom role PackageBMessaging.send 

The reason I have this package based UserRole setup is that these packages are called by individual systems and house all the iflows being used only by one particular sender (so far we didnt have any overlaps between packages)

Now PackageA consumer needs to access another iFlow that exists in PackageB that happens to be an ODATA API exposed via the http sender adapter. Http Sender adapter doesnt have a provision for multiple Userroles and supports only one user role at a time. I want to avoid duplicating this iflow on another http sender endpoint and I want to reuse the existing iflow. How can I do that?

I do not want to share the PackageBMessaging.send credentials with Package A consumer and I also dont want to add PackageBMessaging.send Role in the BTP cockpit instance that I have for PackageA.

[vinaymittal]

I got the answer after some digging.

[vinaymittal]

I got the answer after some digging.

If PackageA Consumer wants to consume a iflow in PackageB then We should create a new User Role lets call it "CommonPackageBMessaging.Send" and the iflow thats to be shared we change the user role to "CommonPackageBMessaging.Send" as well.

In the BTP cockpit, process integration runtime instance for the PackageAMessaging.send user role , do an "update" parameter and "add" this newly created role "CommonPackageBMessaging.Send" so that the PackageA consumer can now access iflows withotu any change in their credentials.

Repeat the same steps as above for PackageBMessaging.send's BTP cockpit pir instance.