This simple example is for those who need to invoke Process from VB with identity propagation. This is a common requirement, when the person is a registered user of both apps, i.e. the pre-requisite for our VB user is that they are also a valid Process user. Ergo, the VB user needs to be added to the target OPA process, with at least the use permission. This you do in the Process Workspace --> Administration --> Roles.
Communication is over a VB Service connection, more about that later.
My VB app is simple, so is the Process -
Step 1 - Create a confidential app in IDCS
- JWT Assertion - will be used by VB
- Refresh Token
- Authorization Code - will be used by my Postman sanity test
Step 2 - Postman Sanity Test & Visual Builder setup
- Your IDCS URL
- Client Id / Secret
- Sample Request Payload for your Process invoke
- The OPA REST API to invoke
I could create a backend entry for OPA, this would include the server data - base url / security settings etc. Multiple service connections could then leverage this, saving me having to enter the server information for each connection.