This repository contains all TypeScript and JavaScript packages and applications you need to create your own ZITADEL Login UI. The repo makes use of the build system Turbo and the Changesets CLI for versioning the packages.
The scope of functionality of this repo and packages is limited and under active development. Once the package structure is set and all APIs are fully implemented we'll move this repo to beta state. You can read the contribution guide on how to contribute. Questions can be raised in our Discord channel or as a GitHub issue.
We think the easiest path of getting up and running, is the following:
- Fork and clone this repository
- Run the ZITADEL Cloud login UI locally
- Make changes to the code and see the effects live on your local machine
- Study the rest of this README.md and get familiar and comfortable with how everything works.
- Decide on a way of how you want to build and run your login UI. You can reuse ZITADEL Clouds way. But if you need more freedom, you can also import the packages you need into your self built application.
login
: The login UI used by ZITADEL Cloud, powered by Next.js@zitadel/server
: core components for establishing node client connection, grpc stub@zitadel/client
: core components for establishing web client connection, grpc stub@zitadel/react
: shared React utilities and components built with tailwindcss@zitadel/next
: shared Next.js utilities@zitadel/tsconfig
: sharedtsconfig.json
s used throughout the monorepoeslint-config-zitadel
: ESLint preset
Each package and app is 100% TypeScript.
- TypeScript for static type checking
- ESLint for code linting
- Prettier for code formatting
pnpm generate
- Build proto stubs for server and client packagepnpm build
- Build all packages and the login apppnpm test
- Test all packages and the login apppnpm test:watch
- Rerun tests on file changepnpm dev
- Develop all packages and the login apppnpm lint
- Lint all packagespnpm changeset
- Generate a changesetpnpm clean
- Clean up allnode_modules
anddist
folders (runs each package's clean script)
Package publishing has been configured using Changesets. Here is their documentation for more information about the workflow.
The GitHub Action needs an NPM_TOKEN
and GITHUB_TOKEN
in the repository settings. The Changesets bot should also be installed on the GitHub repository.
Read the changesets documentation for more information about this automation
If you want to publish a package to the public npm registry and make them publicly available, this is already setup.
To publish packages to a private npm organization scope, remove the following from each of the package.json
's
- "publishConfig": {
- "access": "public"
- },
See working with the npm registry
To run the application make sure to install the dependencies with
pnpm install
then setup the environment for the login application which needs a .env.local
in /apps/login
.
Go to your instance and create a service user for the application having the IAM_OWNER manager role.
This user is required to have access to create users on your primary organization and reading policy data so it can be restricted to your personal use case but we'll stick with IAM_OWNER for convenience. Create a PAT and copy the value to paste it under the ZITADEL_SERVICE_USER_TOKEN
key.
The file should look as follows:
ZITADEL_API_URL=[yourinstanceurl]
ZITADEL_ORG_ID=[yourprimaryorg]
ZITADEL_SERVICE_USER_TOKEN=[yourserviceuserpersonalaccesstoken]
then generate the GRPC stubs with
pnpm generate
and then run it with
pnpm dev
Open the login application with your favorite browser at localhost:3000
.
To deploy your own version on Vercel, navigate to your instance and create a service user. Copy its id from the overview and set it as ZITADEL_SERVICE_USER_ID. Then create a personal access token (PAT), copy and set it as ZITADEL_SERVICE_USER_TOKEN, then navigate to your instance settings and make sure it gets IAM_OWNER permissions. Finally set your instance url as ZITADEL_API_URL. Make sure to set it without trailing slash.