Login Client PAT not generated
āļøConfigurationš¬Self-hostedāQuestionāUnsolved
Use-case: As Authentication Provider for a web application.
Environment: Trying out Self Hosting for local development (On MacOS)
Version: v2.54.8
Stack: Not relevant for the question
Attachments: Screenshots, videos, GIFs, code snippets / APIs (where applicable), & error codes.
I am just starting with Zitadel as a self-hosted variant for our local development. I downloaded the latest docker-compose.yaml and tried to run it. The Login Container does not start up. After checking a bit I found that the .pat Token for
I uncommented the parts about the
What else do I need to do to get the token for the Login?
I don't see any failed migrations in the log files upon start up.
Environment: Trying out Self Hosting for local development (On MacOS)
Version: v2.54.8
Stack: Not relevant for the question
Attachments: Screenshots, videos, GIFs, code snippets / APIs (where applicable), & error codes.
I am just starting with Zitadel as a self-hosted variant for our local development. I downloaded the latest docker-compose.yaml and tried to run it. The Login Container does not start up. After checking a bit I found that the .pat Token for
ZITADEL_FIRSTINSTANCE_LOGINCLIENTPATPATHZITADEL_FIRSTINSTANCE_LOGINCLIENTPATPATH is not generated. I uncommented the parts about the
ORG MachineORG Machine user and that token shows up in my local directory. What else do I need to do to get the token for the Login?
I don't see any failed migrations in the log files upon start up.
