-
Notifications
You must be signed in to change notification settings - Fork 2
Zitadel : How to setup and configure the PIX ‐ Identity Management
Refer to the documentation on https://zitadel.com/docs in case something is unclear.
In case you wish to create the zitadel instance from scratch, here's how to do it:
- Create a docker compose according to the documentation: https://zitadel.com/docs/self-hosting/deploy/compose
- Configure the Zitadel instance on creation with the following config files: https://zitadel.com/docs/self-hosting/manage/configure
When you preconfigure the Zitadel instance, you will still have to configure the Projects/Application in Zitadel itself. You can only preconfigure the Organization setup. (Zitadel does support Terraform, I have not meddled with that, but feel free to try :) )
Depending on how you set up the instance, the root login and password are in your config files or you can find them somewhere on the links posted in II. Log into the instance and go to Projects tab. (You may be asked to change your password on first login.)
Click "create a new project" and name it.
- Once created, create a new Application in the project. Depending on the type of project you want, the choice can differ. We choose: "Web application".
- Choose your preferred authentication system, we use the recommended PKCE.
- Configure the callback and redirect url, this is optional and can be configured later.
- Copy the generated client-ID (project_id@name_of_application)
In Token settings, don't forget to enable the checkbox: "User Info inside ID Token". This allows us to extract the user information from Zitadel for use in our own application.
Remember when working in a dev environment or you dont need HTTPS yet, enable the "Development mode" selector in the "Redirect Settings".
The URL's tab contains all of the important url's as well as the Discovery Endpoint configuration.
Not everyone will be able to set up an email server. This prevents you from creating new users from the register screen. Luckily we can use the API to circumvent this restriction.
- In the Users tab, select Service Users and create a new user.
- Enter the details for the new user and select Bearer token.
- Store the token somewhere safe as it will not be accesible anymore after closing the creation screen.
- Add the newly created service user to the Project Admin group with the required roles for the manipulations you wish to do. (User mangement, ...) We can now append this token to API requests like https://zitadel.com/docs/apis/resources/mgmt/management-service-add-human-user (SOON TO BE DEPRECATED)
You should now have successfully configured the Zitadel instance to get started. More information can always be found in the Documentation, as well as their discord server, where devs will actively help you out if you run into trouble. (Github also still exists but is slower in response time)
-
Archive (ignore this, for history reasons only)
- Jonas' Notes
- Developer Notes
- System Design
-
Developer Notes
-
System Design
-
Policies