The new version of the Pipeline Engine provides a new feature to dynamically configure the credentials for each pipeline run.
Currently, this feature is in the Restricted Beta phase and is only available to specific customers.
In the current version of the Pipeline Engine of the Digibee Integration Platform, account configuration is done statically, and it is not possible to change them at runtime. This can slow down processes in some scenarios. For example: receiving a certificate from an endpoint and authenticating in a REST API or receiving an ephemeral authentication token for dynamic authentication over an SFTP. Now, customers who use multipurpose pipelines on the Digibee Integration Platform can change their credentials configurations on the Runtime screen, through the new Store Account component.
With the new functionality, Digibee simplifies credential management, providing greater agility and security at all stages of your workflow. Now it will be possible to support dynamic accounts for Digibees Customers using Engine v2.
The dynamic accounts functionality allows you to adapt account settings to the specific needs of each connector, maximizing the efficiency of your integrations and processes. This update is available as a new parameter configuration for the following Digibee Integration Platform components:
The new configuration parameters are available in the documentation of each of their respective components.
For your security, never store credentials openly anywhere, nor save them in the Object Store.
To add your dynamic credentials to the pipeline on the canvas, just follow these steps:
Drag the Store Account connector from the components list onto the canvas.
Select the type of account you want to register.
Enter the required credentials.
Click save and run.
Your credentials are now dynamically available on every pipeline run, ready to be referenced by other connectors.
It is very simple to use dynamic accounts in components:
Enable the Use Dynamic Accounts option on the desired connector (See list of components above).
Enter the name of the account previously created with the Store Account component in the Account Name field.
The connector is now ready to authenticate using this credential.
To use the account scope in the body of requests in connectors such as REST V2 and SOAP v3, just register the credential {{ account.custom-1.password }} using the Store Account connector. That way, you can easily use this information in your operations.
For example, a BASIC type account was created using the Store Account and the name given to it was account-test. it will be enough to inform it like this: {{account.account-test-password }}.
Use of the Store Account component in parallel scenarios, such as parallel execution or For Each, is not recommended on the Restricted Beta Phase.
Last updated
Was this helpful?
Was this helpful?
