Florian M

> Currently not as I understand it Making the first user of the orga admin sounds like a good idea. > Do you want another route to check that? The...

If I understand this correctly, there is currently no way of creating a new orga via oidc, right? I’d even think there is no way to create an empty organization...

> If the name was updated in keycloak, wk will still show the old name I’d say this is pretty harmless. If a user reports a divergence, it is trivial...

Any chance we could rename features.oidcEnabled to features.openIdConnectEnabled? That would be more consistent with the other application.conf keys. (As mentioned above we tried to avoid the acronym for consistency)

@frcroth what exactly is OIDC Implicit flow? I noticed that in the steps to test the client has `implicitFlowEnabled: false` but you named the PR this way – does that...

Thanks! > but I couldn't build them new after yarn remove-snapshots with docker compose up e2e-tests failing did that work before? `yarn refresh-snapshots` is the standard way now, but I...

`yarn install` was the right call for the failing snapshot tests. The new lib `lz4-wasm` was added in #6652 and `rome` was added in https://github.com/scalableminds/webknossos/pull/6618 – so this is likely...

The “explore” route inspects wkw headers (or zarr/n5/precomptued metadata files) and sets the value for the datasource-proprties.json. This only happens once during explore, but we might want to do this...

I went through the code and came to the conclusion that we can probably go ahead with this as intended without major changes. The worker currently uses the webknossos_token only...

Ok, sounds fair! Follow-up for the UI changes: https://github.com/scalableminds/webknossos/issues/7734