58b01cdf3f
* idp list, idp create route * idp modules, lazy import, i18n, routing * generic service, i18n * seperate lockout, age policy component * seperate component modules * routing * enum class * login policy * iam policy grid * login policy providers * idps login policy * add idp dialog component * add idp to loginpolicy * delete idp config, iam policy grid * remove idp from loginpolicy * idp detail component, generic idp create * lint * idp detail clientid-secrets, issuer, scopes * hide clientsecret on update * rm background style, idp config * app tooltip fix * lint * dont refresh on idp select * Update console/src/app/modules/idp-create/idp-create.component.html Co-authored-by: Fabiennne <fabienne.gerschwiler@gmail.com> Co-authored-by: Fabi <38692350+fgerschwiler@users.noreply.github.com> |
||
|---|---|---|
| .codecov | ||
| .github | ||
| build | ||
| cmd/zitadel | ||
| console | ||
| docs | ||
| internal | ||
| k8s/base | ||
| migrations/cockroach | ||
| pkg/grpc | ||
| site | ||
| .gitignore | ||
| .releaserc.js | ||
| go.mod | ||
| go.sum | ||
| LICENSE | ||
| README.md | ||
| SECURITY.md | ||
This project is in a alpha state. The application will continue breaking until version 1.0.0 is released
What Is It
ZITADEL is a Cloud Native Identity and Access Management solution. All server side components are written in Go and the management interface, called Console, is written in Angular.
We optimized ZITADEL for the usage as service provider IAM. By service provider we think of companies who build services for e.g SaaS cases. Often these companies would like to use an IAM where they can register their application and grant other people or companies the right to self manage a set of roles within that application.
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 eventsourced 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.
Why Another IAM
In the past we already built a closed sourced IAM and tested multiple others. With most of them we had some issues, either technology, feature, pricing or transparency related in nature. For example we find the idea that security related features like MFA should not be hidden behind a paywall or a feature price.
One feature that we often missed, was a solid audit trail of all IAM resources. Most systems we saw so far either rely on simple log files or use a short retention for this.
How To Use It
Use our free tier
Stay tuned, we will publish how you can register an organisation in our cloud offering zitadel.ch soon.
Yes we have a free tier!
Run your own IAM
Stay tuned, we will soon publish a guide how you can deploy a hyperconverged system with our automation tooling called ORBOS.
With ORBOS you will be able to run ZITADEL on GCE or StaticProvider within 20 minutes. To achieve this, ORBOS will bootstrap and maintain a Kubernetes cluster, essential platform components (logging, metrics, ingress, ...), a secure CockroachDB cluster and ZITADEL itself.
The combination of the tools ORBOS and ZITADEL is what makes the operation easy and scalable.
See our progress here
Give me some docs
This is work in progess but will change soon.
How To Contribute
TBA
Security
See the policy here
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.