Skip to content

Commit 43b7c9e

Browse files
AaronDewesAaronDewes
committed
Merge branch 'main' of github.com:zitadel/zitadel
2 parents 421ceaf + b5d7518 commit 43b7c9e

411 files changed

Lines changed: 4839 additions & 4365 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

‎ADOPTERS.md‎

Lines changed: 26 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -1,30 +1,34 @@
11
## Adopters
22

3-
Sharing experiences and learning from other users is essential. We are frequently asked who is using a particular feature of Zitadel so people can get in touch with other users to share experiences and best practices. People also often want to know if a specific product or platform has integrated Zitadel. While the Zitadel Discord Community allows users to get in touch, it can be challenging to find this information quickly.
3+
Sharing experiences and learning from other users is essential. We are frequently asked who is using a particular
4+
feature of Zitadel so people can get in touch with other users to share experiences and best practices. People also
5+
often want to know if a specific product or platform has integrated Zitadel. While the Zitadel Discord Community allows
6+
users to get in touch, it can be challenging to find this information quickly.
47

5-
The following is a directory of adopters to help identify users of individual features. The users themselves directly maintain the list.
8+
The following is a directory of adopters to help identify users of individual features. The users themselves directly
9+
maintain the list.
610

711
### Adding yourself as a user
812

9-
If you are using Zitadel, please consider adding yourself as a user with a quick description of your use case by opening a pull request to this file and adding a section describing your usage of Zitadel.
13+
If you are using Zitadel, please consider adding yourself as a user with a quick description of your use case by opening
14+
a pull request to this file and adding a section describing your usage of Zitadel.
1015

11-
| Organization/Individual | Contact Information | Description of Usage |
12-
| ----------------------- | -------------------------------------------------------------------- | ----------------------------------------------- |
13-
| Zitadel | [@fforootd](https://github.com/fforootd) (and many more) | Zitadel Cloud makes heavy use of of Zitadel ;-) |
14-
| Rawkode Academy | [@RawkodeAcademy](https://github.com/RawkodeAcademy) | Rawkode Academy Platform & Zulip use Zitadel for all user and M2M authentication |
15-
| XPeditionist | [@XPeditionistTravel](https://github.com/XPeditionistTravel) | An innovative all-in-one travel solution use Zitadel as complete auth solution. |
16-
| devOS: Sanity Edition | [@devOS-Sanity-Edition](https://github.com/devOS-Sanity-Edition) | Uses SSO Auth for every piece of our internal and external infrastructure |
17-
| CNAP.tech | [@cnap-tech](https://github.com/cnap-tech) | Using Zitadel for authentication and authorization in cloud-native applications |
18-
| Minekube | [@minekube](https://github.com/minekube) | Leveraging Zitadel for secure user authentication in gaming infrastructure |
19-
| Dribdat | [@dribdat](https://github.com/dribdat) | Educating people about strong auth and resilient identity at hackathons |
20-
| Micromate | [@sschoeb](https://github.com/sschoeb) | Using Zitadel for authentication and authorization for learners and managers in our digital learning assistant as well as in the Micromate manage platform |
21-
| Smat.io | [@smatio](https://github.com/smatio) - [@lukasver](https://github.com/lukasver) | Zitadel for authentication in cloud applications while offering B2B portfolio management solutions for professional investors |
22-
|hirschengraben | [hirschengraben.io](hirschengraben.io) | Using Zitadel as IDP for a multitenant B2B dispatch app for bike messengers |
23-
| OpenAIP | [@openaip](https://github.com/openAIP) | Using Zitadel Cloud for everything related to user authentication. |
24-
| Smat.io | [@smatio](https://github.com/smatio) - [@lukasver](https://github.com/lukasver) | Zitadel for authentication in cloud applications while offering B2B portfolio management solutions for professional investors |
25-
| roclub GmbH | [@holgerson97](https://github.com/holgerson97) | Roclub builds a telehealth application to enable remote MRI/CT examinations. |
26-
| CEEX AG | [@cleanenergyexchange](https://github.com/cleanenergyexchange) | Using Zitadel cloud for our SaaS products that support the sustainabel energy transistion |
27-
| D1V.AI | [d1v.ai](https://d1v.ai) | Powering the *fastest way from prompt to profit*. Zitadel Cloud delivers the secure, scalable user authentication that makes our vibe coding platform possible. |
28-
| Organization Name | contact@example.com | Description of how they use Zitadel |
29-
| Individual Name | contact@example.com | Description of how they use Zitadel |
16+
| Organization/Individual | Contact Information | Description of Usage |
17+
|-------------------------|---------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|
18+
| Zitadel | [@fforootd](https://github.com/fforootd) (and many more) | Zitadel Cloud makes heavy use of of Zitadel ;-) |
19+
| Rawkode Academy | [@RawkodeAcademy](https://github.com/RawkodeAcademy) | Rawkode Academy Platform & Zulip use Zitadel for all user and M2M authentication |
20+
| XPeditionist | [@XPeditionistTravel](https://github.com/XPeditionistTravel) | An innovative all-in-one travel solution use Zitadel as complete auth solution. |
21+
| devOS: Sanity Edition | [@devOS-Sanity-Edition](https://github.com/devOS-Sanity-Edition) | Uses SSO Auth for every piece of our internal and external infrastructure |
22+
| CNAP.tech | [@cnap-tech](https://github.com/cnap-tech) | Using Zitadel for authentication and authorization in cloud-native applications |
23+
| Minekube | [@minekube](https://github.com/minekube) | Leveraging Zitadel for secure user authentication in gaming infrastructure |
24+
| Dribdat | [@dribdat](https://github.com/dribdat) | Educating people about strong auth and resilient identity at hackathons |
25+
| Micromate | [@sschoeb](https://github.com/sschoeb) | Using Zitadel for authentication and authorization for learners and managers in our digital learning assistant as well as in the Micromate manage platform |
26+
| Smat.io | [@smatio](https://github.com/smatio) - [@lukasver](https://github.com/lukasver) | Zitadel for authentication in cloud applications while offering B2B portfolio management solutions for professional investors |
27+
| hirschengraben | [hirschengraben.io](hirschengraben.io) | Using Zitadel as IDP for a multitenant B2B dispatch app for bike messengers |
28+
| OpenAIP | [@openaip](https://github.com/openAIP) | Using Zitadel Cloud for everything related to user authentication. |
29+
|  roclub GmbH |  [@holgerson97](https://github.com/holgerson97) |  Roclub builds a telehealth application to enable remote MRI/CT examinations. |
30+
|  CEEX AG |  [@cleanenergyexchange](https://github.com/cleanenergyexchange) |  Using Zitadel cloud for our SaaS products that support the sustainabel energy transistion |
31+
|  D1V.AI |  [d1v.ai](https://d1v.ai) |  Powering the *fastest way from prompt to profit*. Zitadel Cloud delivers the secure, scalable user authentication that makes our vibe coding platform possible. |
32+
| Organization Name | contact@example.com | Description of how they use Zitadel |
33+
| Individual Name | contact@example.com | Description of how they use Zitadel |
3034

‎README.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -187,7 +187,7 @@ Use our Login widget to allow easy and secure access to your applications and en
187187

188188
### Management Console
189189

190-
Use [Console](https://zitadel.com/docs/guides/manage/console/console-overview) or our [APIs](https://zitadel.com/docs/apis/introduction) to setup organizations, projects and applications.
190+
Use [Console](https://zitadel.com/docs/guides/manage/console/console-overview) or our [APIs](https://zitadel.com/docs/apis/introduction) to set up organizations, projects and applications.
191191

192192
[![Console Showcase](https://user-images.githubusercontent.com/1366906/223663344-67038d5f-4415-4285-ab20-9a4d397e2138.gif)](http://www.youtube.com/watch?v=RPpHktAcCtk "Console Showcase")
193193

‎SECURITY.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33
## Introduction
44

55
At ZITADEL we are extremely grateful for security aware people who disclose vulnerabilities to us and the open source community.
6-
All reports will be investigated by our team and we will work with you closely to validate and fix vulnerabilities reported to us.
6+
All reports will be investigated by our team, and we will work with you closely to validate and fix vulnerabilities reported to us.
77

88
We require that you keep vulnerabilities confidential until we are able to address them, since public disclosure of security vulnerabilities could put the ZITADEL community at risk.
99

@@ -32,7 +32,7 @@ To file an incident, please disclose it by e-mail to [security@zitadel.com](mail
3232
At the moment GPG encryption is no yet supported, however you may sign your message at will.
3333

3434
Your email will be acknowledged within 48 hours.
35-
We will follow-up within the next 3 business days indicating next steps in handling your report.
35+
We will follow up within the next 3 business days indicating next steps in handling your report.
3636

3737
If you haven't received a response within 48 hours, or you didn't get a reply from our security team within the last 5 days, please contact [support@zitadel.com](mailto:support@zitadel.com).
3838

@@ -41,7 +41,7 @@ We will not publish this information by default to protect your privacy.
4141

4242
### When should I NOT report a vulnerability
4343

44-
- Disclosure of known public files or directories, e.g. robots.txt, files under .well-known, or files that are included in our public repositories (eg, go.mod)
44+
- Disclosure of known public files or directories, e.g. robots.txt, files under .well-known, or files that are included in our public repositories (e.g. `go.mod`)
4545
- DoS of users when [Lockout Policy is enabled](https://zitadel.com/docs/guides/manage/console/default-settings#lockout)
4646
- You need help applying security related settings
4747

‎apps/docs/README.md‎

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -20,24 +20,24 @@ The site will be available at http://localhost:3000.
2020

2121
Key scripts for documentation workflows:
2222

23-
| Script | Description |
24-
| :--- | :--- |
25-
| `dev` | Starts the development server. |
26-
| `build` | Builds the production application. |
27-
| `fetch:remote-content` | Fetches remote tags and referenced content. |
28-
| `generate` | Runs all generation steps (`fetch:remote-content`, `generate:proto-docs`, `generate:api-reference`, `generate:index-pages`). |
29-
| `check:links` | Validates content integrity (broken links, missing frontmatter, schema errors). |
30-
| `check-types` | Validates typescript types. |
31-
| `test` | Runs all validation steps (`check-types`, `check:links`). |
32-
| `lint` | checks for code style and syntax errors (ESLint). |
33-
| `clean` | Cleans the build output and generated files. |
23+
| Script | Description |
24+
|:-----------------------|:-----------------------------------------------------------------------------------------------------------------------------|
25+
| `dev` | Starts the development server. |
26+
| `build` | Builds the production application. |
27+
| `fetch:remote-content` | Fetches remote tags and referenced content. |
28+
| `generate` | Runs all generation steps (`fetch:remote-content`, `generate:proto-docs`, `generate:api-reference`, `generate:index-pages`). |
29+
| `check:links` | Validates content integrity (broken links, missing frontmatter, schema errors). |
30+
| `check-types` | Validates typescript types. |
31+
| `test` | Runs all validation steps (`check-types`, `check:links`). |
32+
| `lint` | checks for code style and syntax errors (ESLint). |
33+
| `clean` | Cleans the build output and generated files. |
3434

3535
### Validation
3636

3737
* **Code Quality**: Run `pnpm lint` to check for syntax and style issues in JS/TS/MDX files.
3838
* **Content Integrity**: Run `pnpm check:links` to validate content structure, including:
3939
* Broken internal links
40-
* Missing required frontmatter (e.g., `title`)
40+
* Missing required front-matter (e.g., `title`)
4141
* Image references
4242

4343
## Contributing

‎apps/docs/components/PermissionTable/index.jsx‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
import React, { useMemo } from 'react';
22
import yaml from 'js-yaml';
33
import { Check, X } from 'lucide-react';
4-
import { cn } from '@/utils/cn'; // Assuming utils/cn exists or I'll use clsx/tailwind-merge directly if not sure
4+
import { cn } from '@/utils/cn'; // Assuming utils/cn exists, or I'll use clsx/tailwind-merge directly if not sure
55

6-
// Fallback utility if generic cn doesn't exist, checking imports first is safer but I'll inline a simple merge if needed
6+
// Fallback utility if generic cn doesn't exist, checking imports first is safer, but I'll inline a simple merge if needed
77
// Checking package.json I saw clsx and tailwind-merge are dependencies.
88

99
function classNames(...classes) {

‎apps/docs/components/version-selector.tsx‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ export function VersionSelector() {
2020

2121
// Handle basePath issues: usePathname() typically returns path relative to basePath if configured?
2222
// But purely relying on that is tricky. Let's normalize.
23-
// If pathname starts with /docs, assume it's the full path and we strip it for logic,
23+
// If pathname starts with /docs, assume it's the full path, and we strip it for logic,
2424
// then let router handle re-adding it if needed (or we check behaviors).
2525
// Actually, Next.js router.push() expects path relative to basePath usually?
2626
// Let's implement robust segment swapping.

‎apps/docs/content/apis/actions/external-authentication.mdx‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -91,7 +91,7 @@ The trigger is represented by the following Ids in the API: `TRIGGER_TYPE_PRE_CR
9191
- `setLastName(string)`
9292
Sets the last name
9393
- `setNickName(string)`
94-
Sets the nick name
94+
Sets the nickname
9595
- `setDisplayName(string)`
9696
Sets the display name
9797
- `setPreferredLanguage(string)`

‎apps/docs/content/apis/actions/internal-authentication.mdx‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -58,7 +58,7 @@ The trigger is represented by the following Ids in the API: `TRIGGER_TYPE_PRE_CR
5858
- `setLastName(string)`
5959
Sets the last name
6060
- `setNickName(string)`
61-
Sets the nick name
61+
Sets the nickname
6262
- `setDisplayName(string)`
6363
Sets the display name
6464
- `setPreferredLanguage(string)`

‎apps/docs/content/apis/actions/introduction.mdx‎

Lines changed: 0 additions & 58 deletions
This file was deleted.

0 commit comments

Comments
 (0)