38a4683bab
* fix: enum to display access token role assertion * improve assertion descriptions * fix nil pointer |
||
|---|---|---|
| .codecov | ||
| .github | ||
| build | ||
| cmd | ||
| console | ||
| docs | ||
| guides | ||
| hack | ||
| internal | ||
| k8s/base | ||
| migrations | ||
| openapi | ||
| operator | ||
| pkg | ||
| proto/zitadel | ||
| scripts | ||
| tools | ||
| .dockerignore | ||
| .gitignore | ||
| .releaserc.js | ||
| changelog.config.js | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| go.mod | ||
| go.sum | ||
| LICENSE | ||
| README.md | ||
| SECURITY.md | ||
What Is ZITADEL
ZITADEL is a "Cloud Native Identity and Access Management" solution built for the cloud era. ZITADEL uses a modern software stack consisting of Golang, Angular and CockroachDB as sole storage and follows an event sourced pattern.
We built ZITADEL not only with the vision of becoming a great open source project but also as a superb platform to support developers building their applications, without need to handle secure user login and account management themselves.
How Does It Work
We built ZITADEL around the idea that the IAM should be easy to deploy and scale. That's why we tried to reduce external systems as much as possible. For example, ZITADEL is event sourced but it does not rely on a pub/sub system to function. Instead we built all the functionality right into one binary. ZITADEL only needs Kubernetes for orchestration and CockroachDB as storage.
Features of ZITADEL platform
- Authentication
- OpenID Connect 1.0 Protocol (OP)
- Username / Password
- Machine-to-machine (JWT profile)
- Passwordless with FIDO2
- Multifactor authentication with OTP, U2F
- Federation with OpenID Connect 1.0 Protocol (RP), OAuth 2.0 Protocol (RP)
- Authorization via Role Based Access Control (RBAC)
- Identity Brokering
- Delegation of roles to other organizations for self-management
- Strong audit trail for all IAM resources
- User interface for administration
- APIs for Management, Administration, and Authentication
- Policy configuration and enforcement
- Private Labeling
Run ZITADEL anywhere
Self-Managed
You can run an automatically operated ZITADEL instance on a CNCF compliant Kubernetes cluster of your choice:
- CRD Mode on an existing k8s cluster
- GitOps Mode on an existing k8s cluster
- GitOps Mode on VM/bare-metal using ORBOS
CAOS-Managed
- ZITADEL Cloud: ZITADEL.ch is our shared cloud service hosted in Switzerland. Get started and try the free tier, including already unlimited users and all necessary security features.
- ZITADEL Enterprise: We operate and support a private instance of ZITADEL for you. Get in touch!
Start using ZITADEL
Quickstarts
See our Documentation to get started with ZITADEL quickly. Let us know, if you are missing a language or framework in the Q&A.
Client libraries
Help and Documentation
Showcase
Passwordless Login
Use our login widget to allow easy and sucure access to your applications and enjoy all the benefits of passwordless (FIDO 2 / WebAuthN):
- works on all modern platforms, devices, and browsers
- phishing resistant alternative
- requires only one gesture by the user
- easy enrollment of the device during registration
Admin Console
Use Console or our APIs to setup organizations, projects and applications.
Register new applications
Delegate the right to assign roles to another organization
Customize login and console with your design
How To Contribute
Details about how to contribute you can find in the Contribution Guide
Security
See the policy here
Other CAOS Projects
- ORBOS - GitOps everything
- OIDC for GO - OpenID Connect SDK (client and server) for Go
- ZITADEL Tools - Go tool to convert key file to privately signed JWT
License
See the exact licensing terms here
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.