Jinna Kiisuo

With the jank qemu stack I cobbled, could probably just run through a couple of scenarios and see how they behave in practice. All the things you mentioned are probably...

I'll add a quick note that *something* has also changed on the kanidm-unixd side as well between 1.7.3 and the master branch. I say that because the weird startup issues...

It seems to be a Debianism to default enable all services, so in theory it's what users expect. But yes, I imagine there must be some other daemon packaged for...

1.6 is out in the PPA, @candlerb could you do a re-test with the newer version to make sure this was already fixed?

That's probably due to the default config we ship that tries to enable things that can't work on first startup before config. This one is looking at addressing it: https://github.com/kanidm/kanidm/issues/3838

Actually, the data is present for `idm_all_accounts`, so the problem is that documentation refers instead to `idm_all_persons`, which does not have it as per `get` / `list`. > A default...

Looks like #2533 changed the documentation from `idm_all_accounts` to `idm_all_persons` but not clear if that was intentional since the commit messages don't really address that change specifically. My original install...

I think this needs more testing with a clean install to see what the state is before making any policy changes or resets and which one is the shipped default,...

Actually keeping this open for a bit longer since this became a multi-PR, multi-repo kind of affair. While first blocks are in, it'll be a bit longer before the repo...

The launch is out, yay! There are however remaining issues, not yay: - [x] The pipeline correctly creates the GPG public key as an `.asc` file with ASCII armoring, BUT...