Page History
...
| Warning |
|---|
If redis data store is used and the properties for configuring the host and/or the port are missing, the Runtime will not start. |
Authorization
When an external flow is executed on a different runtime than the one that the current project is open, there needs to be a way in order for the roles of the currently logged in user to be validated on the target runtime where the external flow resides to. In order to support this, the authentication details of the main project are saved in the External flow DataStore and when the external flow is executed, the authentication is retrieved on the runtime where the external flow resides on, and is set up as if the same user has logged in on that runtime.
| Warning |
|---|
When an external flow resides on a different Runtime, that Runtime gains access to the authorization details of the user that is executing the external flow, and it may make requests to other systems with that user credentials (especially when using OpenId Connect). |
| Info |
|---|
When executing an external flow on a different runtime, it is mandatory for both runtimes (the current runtime and the one containing the external flow) to have the same authentication type. |
Overview
Content Tools