andwati/zitadel
1
0
Fork 0
mirror of https://github.com/andwati/zitadel.git synced 2026-11-01 03:52:14 +00:00
Code Issues Packages Projects Releases Wiki Activity

chore: naming inconsistency application (#11431)

Browse Source
This commit is contained in:
Wim Van Laer
2026-02-04 07:20:07 +00:00
committed by GitHub
parent 04c58c5b3f
commit 61d4060df3
96 changed files with 22550 additions and 22674 deletions
Download Patch File Download Diff File Expand all files Collapse all files
apps/docs/content/examples/login/angular.mdx
+2 -2
View File
@@ -30,11 +30,11 @@ Continue and create the application.
### Client ID
After successful creation of the app, a pop-up will appear displaying the app's client ID. Copy the client ID, as you will need it to configure your Angular client.
After successful creation of the app, a pop-up will appear displaying the app's client ID. Copy the client ID, as you will need it to configure your Angular application.
## Angular setup
Now that you have configured your web application on the ZITADEL side, you can proceed with the integration of your Angular client.
Now that you have configured your web application on the ZITADEL side, you can proceed with the integration of your Angular application.
### Install Angular dependencies
apps/docs/content/examples/login/go.mdx
+2 -2
View File
@@ -40,13 +40,13 @@ Continue and create the application.
### Client ID
After successful creation of the app, a pop-up will appear displaying the app's client ID. Copy the client ID, as you will need it to configure your Go client.
After successful creation of the app, a pop-up will appear displaying the app's client ID. Copy the client ID, as you will need it to configure your Go application.
![Create app in management console - copy client_id](../../../public/img/go/app-create-clientid.png)
## Go setup
Now that you have configured your web application on the ZITADEL side, you can proceed with the integration of your Go client.
Now that you have configured your web application on the ZITADEL side, you can proceed with the integration of your Go application.
### Install ZITADEL Go SDK
apps/docs/content/examples/login/java-spring.mdx
+2 -2
View File
@@ -40,13 +40,13 @@ Continue and create the application.
### Client ID
After successful creation of the app, a pop-up will appear displaying the app's client ID. Copy the client ID, as you will need it to configure your Java client.
After successful creation of the app, a pop-up will appear displaying the app's client ID. Copy the client ID, as you will need it to configure your Java application.
![Create app in management console - copy client_id](../../../public/img/java-spring/app-create-clientid.png)
## Spring setup
Now that you have configured your web application on the ZITADEL side, you can proceed with the integration of your Spring client.
Now that you have configured your web application on the ZITADEL side, you can proceed with the integration of your Spring application.
This guide will reference the [example repository](https://github.com/zitadel/zitadel-java) and explain the necessary steps taken in there.
If your starting from scratch, you can use the Spring Initializer with the [following setup](https://start.spring.io/#!type=maven-project&language=java&platformVersion=3.2.1&packaging=jar&jvmVersion=17&dependencies=web,thymeleaf,security,oauth2-client,lombok) as a base.
apps/docs/content/examples/login/nextjs-b2b.mdx
+1 -1
View File
@@ -94,7 +94,7 @@ Replace the values as follows
`NEXTAUTH_URL`: Base url of this demo app (B2B portal); runs per default on [http://localhost:3000](http://localhost:3000)
`NEXT_PUBLIC_ZITADEL_ISSUER`: The url to your zitadel instance. When using zitadel.cloud for this demo you can find the domain of your ZITADEL instance in the customer portal. You can also find this information by going to your application `portal-web` and click 'URLs' in the navigation. The variable is prefixed with `NEXT_PUBLIC_` such that it can be accessed from the client.
`NEXT_PUBLIC_ZITADEL_ISSUER`: The url to your zitadel instance. When using zitadel.cloud for this demo you can find the domain of your ZITADEL instance in the customer portal. You can also find this information by going to your application `portal-web` and click 'URLs' in the navigation. The variable is prefixed with `NEXT_PUBLIC_` such that it can be accessed from the application.
`ZITADEL_API`: URL of the Management API. Typically the same as `ZITADEL_ISSUER`.
apps/docs/content/examples/login/nextjs.mdx
+1 -1
View File
@@ -56,7 +56,7 @@ Now that you have your web application configured on the ZITADEL side, you can g
### Configuration
NextAuth.js exposes a REST API which is used by your client.
NextAuth.js exposes a REST API which is used by your application.
To setup your configuration, create a file called `src/lib/auth.ts`.
You can directly import the ZITADEL provider from [next-auth](https://next-auth.js.org/providers/zitadel).
apps/docs/content/examples/login/react.mdx
+3 -3
View File
@@ -38,11 +38,11 @@ Continue and create the application.
### Copy Client ID
After successful creation of the app, make sure copy the client ID, as you will need it to configure your React client.
After successful creation of the app, make sure copy the client ID, as you will need it to configure your React application.
## Create a project role "admin" and assign it to your user
Also note the projects resource ID, as you will need it to configure your React client.
Also note the projects resource ID, as you will need it to configure your React application.
![](../../../public/img/react/project-role.png)
@@ -52,7 +52,7 @@ If you want to read your users roles from user info endpoint, make sure to enabl
## React setup
Now that you have configured your web application on the ZITADEL side, you can proceed with the integration of your React client.
Now that you have configured your web application on the ZITADEL side, you can proceed with the integration of your React application.
### Install React dependencies
apps/docs/content/examples/login/symfony.mdx
+1 -1
View File
@@ -71,7 +71,7 @@ The secret will not be displayed again, but you can regenerate one if you loose
## Setup new Symfony application
Now that you have configured your web application on the ZITADEL side, you can proceed with the integration of your Symfony client.
Now that you have configured your web application on the ZITADEL side, you can proceed with the integration of your Symfony application.
The example is build on a [generated Symfony web app](https://symfony.com/doc/current/setup.html#creating-symfony-applications), using the following command:
<Callout>
apps/docs/content/examples/login/vue.mdx
+3 -3
View File
@@ -39,13 +39,13 @@ Continue and create the application.
### Refresh Token and Client ID
After successful creation of the app, make sure you tick the checkbox to enable refresh tokens.
Also copy the client ID, as you will need it to configure your Vue client.
Also copy the client ID, as you will need it to configure your Vue application.
![](../../../public/img/vue/tick-refresh-token.png)
## Create a project role "admin" and assign it to your user
Also note the projects resource ID, as you will need it to configure your Vue client.
Also note the projects resource ID, as you will need it to configure your Vue application.
![](../../../public/img/vue/project-role.png)
@@ -53,7 +53,7 @@ Also note the projects resource ID, as you will need it to configure your Vue cl
## Vue setup
Now that you have configured your web application on the ZITADEL side, you can proceed with the integration of your Vue client.
Now that you have configured your web application on the ZITADEL side, you can proceed with the integration of your Vue application.
### Install Vue dependencies
apps/docs/content/examples/secure-api/go.mdx
+1 -1
View File
@@ -52,7 +52,7 @@ And make sure to download it, as you won't be able to retrieve it again.
![](../../../public/img/go/api-download_key.png)
Now we need to create a *Personal Access Token* to authenticate the client requests.
Now we need to create a *Personal Access Token* to authenticate the application requests.
On the user view, switch to *Service Users* and create a new one.
apps/docs/content/examples/secure-api/java-spring.mdx
+2 -2
View File
@@ -25,13 +25,13 @@ Select Basic Auth for authenticating at the Introspection Endpoint.
![Create app in management console](../../../public/img/java-spring/api-create-auth.png)
After successful creation of the app, a pop-up will appear displaying the app's client ID. Copy the client ID and secret, as you will need it to configure your Java client.
After successful creation of the app, a pop-up will appear displaying the app's client ID. Copy the client ID and secret, as you will need it to configure your Java application.
![Create api key in management console](../../../public/img/java-spring/api-create-clientid-secret.png)
## Spring Setup
Now that you have configured your web application on the ZITADEL side, you can proceed with the integration of your Spring client.
Now that you have configured your web application on the ZITADEL side, you can proceed with the integration of your Spring application.
This guide will reference the [example repository](https://github.com/zitadel/zitadel-java) and explain the necessary steps taken in there.
If your starting from scratch, you can use the Spring Initializer with the [following setup](https://start.spring.io/#!type=maven-project&language=java&platformVersion=3.2.1&packaging=jar&jvmVersion=17&dependencies=web,lombok,oauth2-resource-server) as a base.