DD
DD3mo ago

admin.pat is not getting created

ZITADEL_FIRSTINSTANCE_ORG_MACHINE_MACHINE_USERNAME: admin ZITADEL_FIRSTINSTANCE_ORG_MACHINE_MACHINE_NAME: "Automatically Initialized IAM_OWNER" ZITADEL_FIRSTINSTANCE_ORG_MACHINE_MACHINEKEY_TYPE: 1 ZITADEL_FIRSTINSTANCE_PATPATH: /etc/zitadel/admin.pat this not creating admin.pat during the first init. Please help Version is 4.0.0.1
7 Replies
Rajat
Rajat3mo ago
hey @DD what operating system are you on?. https://discord.com/channels/927474939156643850/1405755359641075712/1405848107228336189 /I answer your question here , it should have been auto created
DD
DDOP3mo ago
Debian bookworm
Rajat
Rajat2mo ago
hey @DD does this still exist on Debian?.
DD
DDOP2mo ago
yes. admin pat never gets created. But creates login.pat
Rajat
Rajat2mo ago
hey @DD you need to uncomment these comfigs and try again After that, you need to rerun the setup on a scratch db. We know it's a really bad design, but we have a high prio issue to improve this. I'll add a comment that we also need this for the admin.pat
No description
DD
DDOP2mo ago
Thanks @Rajat . I will try that out
Larzous
Larzous2mo ago
I tried that, but I don’t think it will create a human user and a machine user on the same first instance kickstart. I’ll have to try it again when I have time.

Did you find this page helpful?