-
Hi All, I am aware that there is a fork which includes Oauth 2 , however, I'd rather stick to the original setup, since we do not have in-house Java expertise. Also what are the possibilities that in production, workflows are set to read-only? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 5 replies
-
Hi @azriel46d at Orkes we use Key/Secret for the workers to generate a api token with a set expiry that is used to make all the calls. All the workflows and tasks are protected using Rule Based Access Control and authorization layer which makes it possible to define groups/users with different level of authorization including read-only workflows. This is a layer on top of the OSS without changing the OSS layer or creating a fork of OSS. We do plan to push this to OSS as well in future. |
Beta Was this translation helpful? Give feedback.
Hi @azriel46d at Orkes we use Key/Secret for the workers to generate a api token with a set expiry that is used to make all the calls.
All the workflows and tasks are protected using Rule Based Access Control and authorization layer which makes it possible to define groups/users with different level of authorization including read-only workflows. This is a layer on top of the OSS without changing the OSS layer or creating a fork of OSS. We do plan to push this to OSS as well in future.