mirror of
https://github.com/andwati/zitadel.git
synced 2026-10-30 11:02:16 +00:00
docs: update outdated screenshots (#11630)
# Which Problems Are Solved Update outdated screenshots in the docs. # How the Problems Are Solved By replacing the outdated ones with current screenshots # Additional Changes Replace the usage of "authorization" with "role assignments" in docs where it was previously missed. # Additional Context - Follow-up for PR https://github.com/zitadel/zitadel/pull/11588 - there are some more docs to be updated, which will be done in a following PR --------- Co-authored-by: Copilot <[email protected]>
This commit is contained in:
co-authored by
Copilot
parent
1494f91f80
commit
9b2507832a
@@ -62,7 +62,7 @@ Give the service account a name and a username. Select `Bearer` as *Access Token
|
||||
|
||||

|
||||
|
||||
### Create service account and personal access token (PAT)
|
||||
### Create a service account and a personal access token (PAT)
|
||||
|
||||
Once done, from the left panel of the user management, click on Personal Access Token and create a new one.
|
||||
|
||||
@@ -205,11 +205,11 @@ Finally, create the role as shown below:
|
||||
|
||||

|
||||
|
||||
After you have created the role, let's grant it the user, who requested the tasks.
|
||||
Click on `Authorization` in the navigation and create a new one by selecting the user and the `admin` role.
|
||||
After you have created the role, let's grant it to the user who requested the tasks.
|
||||
Click on `Role Assignments` in the navigation and create a new one by selecting the user and the `admin` role.
|
||||
After successful creation, it should look like:
|
||||
|
||||

|
||||

|
||||
|
||||
So you should now be able to add a new task:
|
||||
|
||||
|
||||
@@ -226,11 +226,11 @@ Finally, create the role as shown below:
|
||||
|
||||

|
||||
|
||||
After you have created the role, let's grant it the user, who requested the tasks.
|
||||
Click on `Authorization` in the navigation and create a new one by selecting the user and the `admin` role.
|
||||
After you have created the role, let's grant it to the user who requested the tasks.
|
||||
Click on `Role Assignments` in the navigation and create a new one by selecting the user and the `admin` role.
|
||||
After successful creation, it should look like:
|
||||
|
||||

|
||||

|
||||
|
||||
So you should now be able to add a new task:
|
||||
|
||||
|
||||
@@ -24,7 +24,7 @@ Before we can start building our application, we have to do a few setup steps in
|
||||
|
||||
<ServiceAccountJWT components={props.components} />
|
||||
|
||||
### Give Service Account an authorization
|
||||
### Assign a role to the Service Account
|
||||
|
||||
<ServiceAccountRole components={props.components} />
|
||||
|
||||
|
||||
@@ -11,7 +11,7 @@ import SetupPython from '../imports/_setup_python.mdx';
|
||||
This integration guide demonstrates the recommended way to incorporate ZITADEL into your Django Python application.
|
||||
It explains how to check the token validity in the API and how to check for permissions.
|
||||
|
||||
By the end of this guide, your application will have three different endpoint which are public, private(valid token) and private-scoped(valid token with specific role).
|
||||
By the end of this guide, your application will have three different endpoints that are public, private (valid token) and private-scoped (valid token with a specific role).
|
||||
|
||||
<Callout>
|
||||
This documentation references our [example](https://github.com/zitadel/example-django-python-oauth) on GitHub.
|
||||
@@ -19,7 +19,7 @@ This documentation references our [example](https://github.com/zitadel/example-d
|
||||
|
||||
## ZITADEL setup
|
||||
|
||||
Before we can start building our application, we have to do a few setup steps in ZITADEL Management Console.
|
||||
Before we can start building our application, we have to do a few setup steps in the ZITADEL Management Console.
|
||||
|
||||
### Create application
|
||||
|
||||
@@ -29,7 +29,7 @@ Before we can start building our application, we have to do a few setup steps in
|
||||
|
||||
<ServiceAccountJWT components={props.components} />
|
||||
|
||||
### Give Service Account an authorization
|
||||
### Assign a role to the Service Account
|
||||
|
||||
<ServiceAccountRole components={props.components} />
|
||||
|
||||
|
||||
@@ -187,7 +187,7 @@ CLIENT_SECRET = "NVAp70IqiGmJldbS...."
|
||||

|
||||
|
||||
1. Create a service account and a Personal Access Token (PAT) for that user by following [this guide](/guides/integrate/service-accounts/personal-access-token#create-a-service-account-with-a-pat).
|
||||
2. To enable authorization, follow [this guide](/guides/manage/console/roles) to create a role `read:messages` on your project.
|
||||
2. To assign roles, follow [this guide](/guides/manage/console/roles) to create a role `read:messages` on your project.
|
||||
3. Next, add the role `read:messages` to the service account you created. Follow this [guide](/guides/manage/console/roles#role-assignments) for more information on creating a role assignment.
|
||||
|
||||
### Run the API
|
||||
|
||||
Reference in New Issue
Block a user