Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update access-control-applications.md #231

Merged
merged 1 commit into from
Dec 12, 2022
Merged

Update access-control-applications.md #231

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/getting-started/concepts/access-control-applications.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ sidebar_position: 4

With [Orkes Cloud](https://orkes.io/cloud/), your Conductor server may be running in a different hosted environment than your workers. The need to restrict access is required to address the security concerns as the APIs are exposed on the internet.

OOrkes has added a security layer called Applications to address such concerns. Every connection in/out of Orkes Cloud requires an Authentication header with a JSON Web Token (JWT) token. This header is of the format: `'X-Authorization: <JWT Token>'`.
Orkes has added a security layer called Applications to address such concerns. Every connection in/out of Orkes Cloud requires an Authentication header with a JSON Web Token (JWT) token. This header is of the format: `'X-Authorization: <JWT Token>'`.

In this document, we will walk through the steps to create application-based control of your workflows and tasks and the process to generate JWT tokens for each application.

Expand Down Expand Up @@ -61,7 +61,7 @@ To add a Workflow/Task permission,
2. In the pop-up window, choose the **Target Type** as Workflow/Task/Secret/Tag.
3. Choose the targets.
4. Choose the permission for the selected targets. The permissions include Read, Create, Update, Execute and Delete.
* **Read** - The user can see the workflow/task but cannot modify or run them.
* **Read** - The user can view the workflow/task but cannot modify or run them.
* **Create** - The user can create the workflow/task.
* **Update** - Allows the user to update the workflow/task. Requires *Metadata API* role for this.
* **Execute** - Allows the user to run the workflow or task. Requires *Worker* role for this.
Expand Down