Skip to main content

Quick start guide


In this quick start guide, we will be learning some fundamentals on how to set up ZITADEL for user management and application security. Thereafter, we will secure a React-based Single Page Application (SPA) using ZITADEL.

The sample application allows users to securely log in to ZITADEL using the OIDC Proof Key for Code Exchange (PKCE) flow. This flow ensures that the authentication process is secure by using a code verifier and a code challenge, which are sent to ZITADEL to obtain an access token. The access token is then used by the app to access the userinfo endpoint to retrieve and display information about the logged-in user. The app also has a logout feature that allows users to end their session and clear their access token. Overall, the app provides a simple and secure way for users to authenticate and access protected resources within ZITADEL.

ZITADEL terminology: instances, organizations, projects, users, roles, authorizations and apps

In ZITADEL, instances, organizations, projects, users, roles, and apps are the main components that make up the platform.

The order of creation for the above components would typically be as follows:

  • Instance: An instance is a top-level entity in ZITADEL that represents a deployment of ZITADEL for a registered account. An instance can have one or more organizations.
  • Organization: An organization is a logical separation within an instance that represents a company/organization and can have one or more projects. The default organization is the one that is provided at the start of the account registration process. Typically, an instance would have one organization, but in B2B scenarios, an instance would have more than one.
  • Project: A project is a logical separation within an organization and is a container for apps, roles and authorization policies for the resources it contains.
  • Users: Users are created at the organizational level and are granted access to the resources within projects. They can be assigned different roles, which define the permissions and privileges they have within the project.
  • Roles: Roles are the sets of permissions and privileges that are assigned to users within a project.
  • Authorizations: Authorization policies in ZITADEL are defined at the project level, which means that they apply to all the resources within the project. These policies are based on the roles that are assigned to users, and they determine the actions that users are allowed to perform within the project.
  • Apps: Apps are the applications that are developed and managed within a project. They can be client apps that use the resources within the project, or they can be backend apps that provide the resources for other apps to use. The apps can use the OIDC or SAML protocol to authenticate users to access protected resources.

The order of creation for the above components may vary depending on the specific needs and requirements of the organization.

Set up and manage ZITADEL for your identity projects

1. Sign up for the ZITADEL Cloud customer portal and register your organization

  1. Go to and click on “Start for FREE”.

Home Page

  1. Enter your details as shown below and click the "Let's go" button.

Registration Page

  1. You will receive a verification email to verify the user for the Customer Portal. Click the “Sign in” button.

Congratulations Page

  1. You will be prompted for a code, which has been emailed to you.


  1. Check your inbox for the code. You can either click the “Finish initialization” button in the email itself or copy the code and return to the previous page. In this guide, we will copy the code and then continue from where we left off.


  1. Paste the code and add a password as shown below. Click on the “next” button.


  1. The user is now activated. Click on “next” to log in.

User Activated

  1. Login with the username and password that you provided. Click “next”.


  1. You should set up 2-factor authentication. However, we will skip this step for now. Click on “skip”.

2-factor Authentication

  1. You will now be asked to create an instance.

Create Instance

2. Create your first instance

As a user of the ZITADEL Cloud Customer Portal, you now can create multiple instances to suit your specific needs. This includes instances for development, production, or user acceptance testing, as well as instances for different clients or applications. For example, you might create an instance for each product in a B2C scenario, or an instance for each tenant or customer in a B2B scenario. The possibilities are endless. You can create a pay-as-you-go instance for production purposes.

  1. Let’s create an instance. Click on “Create new instance”.

Create Instance

  1. Provide a name for your instance, select the “Free” plan and click on the “Continue” button at the bottom of this screen.

Select Tier

  1. Next, you should see the following screen. Add a username and password for the instance manager and click "Create".

Instance Details

  1. The instance creation process will take a few seconds.

Instance Details

  1. Now you will see the details of your first instance. You can click on "Visit" at the top right to go to your instance.

Instance Details

  1. To log in to your instance, provide the username and password, and click “next”.

Instance Details

  1. Skip the 2-factor authentication for now by clicking “skip”.

Instance Details

  1. And there you go! You now have access to your instance.

Access Instance

3. Create your first project

  1. To create a project in the instance you just created, click on “Create Project”.

Create Project

  1. Insert “Project1” (or any name of your choice) as the project’s name and click the “Continue” button.

Project Name

  1. Now you will be taken to the screen below. “Project1” has been created.

Project Created

4. Add users (optional)

Skip optional steps and jump directly to the create application step.

  1. To add users, click on “Users” at the top menu. You will see that the user you already created is listed as a user here. Click on the “New” button to create a new user.

Add User

  1. Let’s add another user as shown below. Fill in the user details as shown below and click on the “Create” button when you are done.

Add User

  1. The newly created user details will be displayed as shown below.

User Info

  1. Once you navigate back to the "Users" view, you will see a list of all the users that have been added to your instance. If you need to add more users, you can do so.

User Info

5. Add roles to your project (optional)

  1. To add roles to your project, click on “Roles” on the left as shown below. Next, click on the “New” button.

Add Roles

  1. Let’s create the role “manager” as shown below. Add “Manager” and “Group1” as display name and group respectively.

Add Role

  1. You can also add other roles in this step by clicking on “Add additional role”. Let’s go ahead and add two more as shown below. Click “Save” when you are done.

Add Role

  1. Now you can view a list of all the roles you just created.

Add Role

6. Add authorizations to your project

  1. Click on “Authorizations” on the top menu.

Add Authorization

  1. Select users for the authorization. You can select 1 or more users for a single authorization grant. Let’s select all the users for this grant.

Add Authorization

  1. Next, select a project. Since we created only “Project1” so far, you will see just that. Go ahead and select it.

Add Authorization

  1. Let’s select the role “sales”. Click on “Save”.

Add Authorization

  1. Now you will see the users with their designated roles.

Add Authorization

  1. To assign additional roles to a user, you can click on the user's name and select the desired roles from the list. This will grant the user additional permissions within the project. Click on “Change”.

Add Authorization

  1. You can see that additional roles have been assigned to the users in this updated authorization list and this should now give you an indication of how authorizations work in ZITADEL.

Add Authorization

7. Create an application in your project

We will now create an application in the project, which will allow our React client application to access protected resources through the use of the OpenID Connect (OIDC) protocol.

  1. Go to “Projects” and click on “Project1”.

Add Application

  1. Click on “New” to add a new application.

Add Application

  1. Provide the name of the app as “React-SPA”. Select “User Agent” and click on “Continue”.

Add Application

  1. Select “PKCE” because we recommend the use of Authorization Code in combination with Proof Key for Code Exchange (PKCE) for all web applications. More about the different app types can be found here. Click on "Continue".

Add Application

  1. The Redirect URL in your application is where the ZITADEL authorization server redirects the user after they have been authenticated. Set your “Redirect URI” to http://localhost:3000/callback and “Post Logout URI” to http://localhost:3000/. Click on “Continue”.

Add Application

  1. Now you will be presented with the details of your application for review. Click on “Create”.

Add Application

  1. After that, a window will appear showing you your “ClientId”. Click on “Close”.

Add Application

  1. On the following screen, you may notice some warnings at the top. These warnings are displayed because the URLs for our application are using unsecure HTTP instead of HTTPS. To resolve this, we will need to update our URLs, but there is a workaround to this so that we can continue using HTTP during the development phase.

Add Application

  1. To proceed with HTTP, go to “Redirect Settings” on the left.

Add Application

  1. Now activate “Development Mode” as shown below and click “Save”.

Add Application

  1. Now if you go to “Projects” and “Project1”, you will see the “React-SPA” app listed as an application in the project:

Add Application

8. Obtain ClientId and OIDC endpoints for your application

You will need the ClientId and the OIDC endpoints (issuer and userinfo) when building your React application. The issuer URL is the base URL for the OIDC provider and includes the path to the OIDC discovery document, which contains information about the OIDC provider, including the authorization and token endpoints. By providing the issuer URL, you can use the OIDC library to automatically determine the endpoints for these requests.

The authorization endpoint is used to initiate the authorization process, the token endpoint is used to exchange authorization codes for access tokens, and the userinfo endpoint is used to retrieve information about the user. You need an access token to access the userinfo endpoint and other protected resources.

  1. Click on “Configurations” to access the Client ID as shown below:

Get URLs

  1. The issuer URL and userinfo endpoint can be accessed by clicking on “URLs” on the left. Make note of the corresponding values for “issuer” and “userinfo_endpoint”.

Get URLs

And with that, configuring ZITADEL for our application is complete. Now we can move on to building our React application. Let's get coding!

Create your React application with ZITADEL OIDC PKCE authentication

1. Functional requirements of the application

  1. The user navigates to the React app (client) and clicks the "login" button.
  2. The app initiates the authorization process by redirecting the user’s browser to the authorization endpoint of the ZITADEL instance, along with the PKCE parameters (code challenge, and code challenge method).
  3. The user will see the ZITADEL login page, where the user can enter their credentials.
  4. After successful authentication, ZITADEL generates an authorization code and redirects the user back to the React app.
  5. The React app sends a request to the ZITADEL token endpoint, along with the authorization code and code verifier.
  6. ZITADEL verifies the code verifier to ensure that the authorization request is coming from the same client that initiated it. If it is valid, ZITADEL returns an access token to the React app.
  7. The React app uses the access token to make a request to the userinfo endpoint, which is protected by the OIDC protocol.
  8. The userinfo endpoint returns information about the logged-in user, such as their name and email address.
  9. The React app displays this information to the user.
  10. When the user wants to log out, the React app sends a request to the ZITADEL logout endpoint, which clears the access token and ends the user's session.
  11. The user will be redirected to the login page of the app.

The scope of this application for this quick start guide is limited to user authentication and doesn't include role-based authentication, even though we previously discussed adding roles and users.

2. Prerequisites

To follow along with this tutorial, you will need to have both React and Visual Studio Code (VSCode) installed on your machine.


To install React, you will need to have Node.js installed on your system. You can download and install Node.js from here.

Once you have Node.js installed, you can use the following command to install React:

npm install -g react

This will install the latest version of React globally on your system. You can then verify the installation by running the following command:

react -v

This should output the version of React that you have installed.

Visual Studio Code

To install Visual Studio Code, go to their website and download and install the version for your operating system.

3. Development

1. Create project

  1. Open a new terminal window in Visual Studio Code.

  2. Navigate to the folder where you want to create the React app.

  3. Run the following command to create a new React app named "react-oidc-zitadel":

    npx create-react-app react-oidc-zitadel

  4. Navigate to the "react-oidc-zitadel" folder:

    cd react-oidc-zitadel

This will create the following files in your project:

  1. The dependencies for this project include react-router-dom and oidc-client-ts. To include them in your React application, you will need to run the following command in your terminal:

    npm install react-router-dom oidc-client-ts

2. Add source files

The code needed to run this project can be found here.

  1. Replace the content in your App.js file with the one provided below:


import React, { useState, useEffect } from "react";
import { BrowserRouter, Routes, Route } from "react-router-dom";
import Login from "./components/Login";
import Callback from "./components/Callback";
import authConfig from "./authConfig";
import { UserManager, WebStorageStateStore } from "oidc-client-ts";

function App() {
const userManager = new UserManager({
userStore: new WebStorageStateStore({ store: window.localStorage }),

function authorize() {
userManager.signinRedirect({ state: "a2123a67ff11413fa19217a9ea0fbad5" });

function clearAuth() {

const [authenticated, setAuthenticated] = useState(null);
const [userInfo, setUserInfo] = useState(null);

useEffect(() => {
userManager.getUser().then((user) => {
if (user) {
} else {
}, [userManager]);

return (
element={<Login auth={authenticated} handleLogin={authorize} />}

export default App;

The App.js file is the root component of the React app that initializes the OIDC flow and manages the user's session. It does this by:

  • Importing the necessary libraries and components from the dependencies, including the oidc-client-ts library, the authConfig file with the OIDC configuration values, and the Login and Callback components.
  • Initializing a new UserManager instance with the OIDC configuration values from the authConfig file. The UserManager instance manages the OIDC flow and stores the user's session information.
  • Defining two functions: authorize and clearAuth. The authorize function initiates the OIDC flow when the user clicks the login button, while the clearAuth function ends the user's session when the user clicks the logout button.
  • Defining two state variables: authenticated and userInfo. The authenticated variable is a boolean that indicates whether the user is authenticated or not, while the userInfo variable stores the user's information when they are authenticated.
  • Using the useEffect hook to retrieve the user's session information from the UserManager instance and updating the authenticated and userInfo state variables accordingly.
  • Defining the routes for the app using the react-router-dom library, including the / and /callback routes for the login and callback pages, respectively. The Login and Callback components handle the login and callback processes, respectively.
  1. Create a folder named components in the src directory. Create two files named Login.js and Callback.js.

  2. Paste the following code to Login.js.


import { Navigate } from "react-router-dom";

const Login = ({ auth, handleLogin, userManager }) => {
return (
{auth === null && <div>Loading...</div>}
{auth === false && (
onClick={() => {
// Perform the authorization request, including the code challenge
Please log in.
{auth && <Navigate to="/callback" />}

export default Login;

The / route corresponds to the login page, which is rendered by the Login component. The Login(Login.js) component is a functional component that displays the login button and calls the handleLogin function (which corresponds to the authorize function defined in the App component) when the button is clicked. This initiates the OIDC flow by redirecting the user to the authorization endpoint.

  1. Paste the following code to Callback.js.


import React, { useEffect } from 'react';
import authConfig from '../authConfig';

const Callback = ({ auth, setAuth, userManager, userInfo, setUserInfo, handleLogout }) => {

useEffect(() => {
if (auth === null) {
userManager.signinRedirectCallback().then((user) => {
if (user) {
const access_token = user.access_token;
// Make a request to the user info endpoint using the access token
fetch(authConfig.userinfo_endpoint, {
headers: {
'Authorization': `Bearer ${access_token}`
.then(response => response.json())
.then(userInfo => {
} else {
}).catch((error) => {
}, [auth, userManager, setAuth]);

if (auth === true && userInfo) {
return (
<h1>Welcome, {}!</h1>
<h2>Your ZITADEL Profile Information</h2>
<h3>Name: {}</h3>
<h3>Email: {}</h3>
<h3>Email Verified: {userInfo.email_verified? "Yes": "No"}</h3>
<h3>Locale: {userInfo.locale}</h3>

<button onClick={handleLogout}>Log out</button>
else {
return <div>Loading...</div>;


export default Callback;

The /callback route corresponds to the callback page, which is rendered by the Callback(Callback.js) component. The Callback component is also a functional component that handles the callback from the authorization server after the user logs in. It retrieves the authorization code from the URL, exchanges it for an access token and id token, and retrieves the user's information from the userinfo endpoint. It also sets the authenticated and userInfo state variables in the App(App.js) component and displays the logout button. When the logout button is clicked, the clearAuth function is called and the user's session is ended. The clearAuth function is defined in the App component and is called with no arguments. It initiates the end session flow by redirecting the user to the end session endpoint.

  1. Create a new file in the src folder named authConfig.js and paste the following code to it.


const authConfig = {
authority: '', //Replace with your issuer URL
client_id: 'ABC123@Project', //Replace with your client id
redirect_uri: 'http://localhost:3000/callback',
response_type: 'code',
scope: 'openid profile email',
post_logout_redirect_uri: 'http://localhost:3000/',
userinfo_endpoint: '', //Replace with your user-info endpoint
response_mode: 'query',
code_challenge_method: 'S256',

export default authConfig;

The authConfig.js file exports an object with configuration values for the OIDC flow. These values are used to initialize the UserManager instance in the App component. The configuration values include the:

  • authority (the URL of the authorization server). Don’t forget to replace the authority value with the “issuer URL” that you obtained from this step.
  • client_id (the unique identifier for the client application). Don’t forget to replace the client_id with your “ClientId” that you obtained from this step.
  • redirect_uri (the URL to redirect to after the authorization flow is complete)
  • response_type (the type of response expected from the authorization server)
  • scope (the permissions requested from the user)
  • post_logout_redirect_uri (the URL to redirect to after the user logs out)
  • userinfo_endpoint (the URL of the endpoint to retrieve the user's information). Don’t forget to replace the userinfo_endoint with your “userinfo_endpoint” that you obtained from this step.
  • response_mode (the method to use to send the authorization response)
  • code_challenge_method (the method to use to generate the code challenge).

Note that the oidc-client-ts library automatically handles the generation of the code verifier and code challenge when the user clicks on the login button, eliminating the need for the application to manually generate and include these values in the requests.

In the PKCE flow, the code verifier is a random string generated by the client application, and the code challenge is a transformed version of the code verifier using the SHA-256 hashing algorithm.

  1. Add a file called style.css to the src folder to apply CSS styling to the pages.


/* The body element covers the entire page, so setting the background color here
will set the background color for the whole page */
body {
font-family: 'Open Sans', sans-serif;
/* The hex code for the light blue color from the image is #9fd3e0 */
background-color: #9fd3e0;
/* Center the text in the body element */
text-align: center;

/* The h1, h2, and h3 elements are used for headings */
h1, h2, h3 {
/* The hex code for the dark blue color from the image is #2c3e50 */
color: #2c3e50;
text-align: center;

/* The button element represents a clickable button */
button {
/* The hex code for the light purple color from the image is #9b59b6 */
background-color: #9b59b6;
/* The hex code for the white color is #ffffff */
color: #ffffff;
/* Add some padding and a border to the button */
padding: 10px 20px;
border: none;
/* Add some hover effect to the button */
cursor: pointer;

button:hover {
/* The hex code for the dark purple color from the image is #8e44ad */
background-color: #8e44ad;
  1. Go to index.js and replace import './index.css'; with import './style.css'. Your index.js file should look like this:


import React from 'react';
import ReactDOM from 'react-dom/client';
import './style.css';
import App from './App';
import reportWebVitals from './reportWebVitals';

const root = ReactDOM.createRoot(document.getElementById('root'));
<App />

// If you want to start measuring performance in your app, pass a function
// to log results (for example: reportWebVitals(console.log))
// or send to an analytics endpoint. Learn more:

4. Running the application

  1. Run npm start to start the development server.
  2. Open your browser and navigate to http://localhost:3000/ to view the app.
  3. You will see the login page, which is the landing page of the app, when you run the application. Click on the “Please log in” button.


  1. You will be redirected to the ZITADEL login page. Add your username/email and click on “next”.


  1. Enter your password and click on “next”.


  1. If you entered the correct login credentials (and if the PKCE parameters generated by the application match), you will be redirected to the callback page, which displays your user information.


  1. You can click on “Log out” to log out of the application and you will be taken to the landing page.


  1. To see if the user has been successfully logged out and the user session has been terminated, click on “Please log in”, which brings you to the following page. Select the same user you logged in with earlier.


  1. You will see that since the login session was terminated after logging out, the user has to enter his password again.


And this brings us to the end of this quick start guide!

This tutorial covered how to configure ZITADEL and how to use React to build an app that communicates with ZITADEL to access secured resources.

We hope you enjoyed the tutorial and encourage you to check out the ZITADEL documentation for more information on how to use the ZITADEL platform to its full potential. Thanks for joining us!