frcroth

You can use keycloak. Put the following into a `docker-compose.yaml` and start it with `docker compose up`. ``` version: '3' volumes: mysql_data: driver: local services: mysql: image: mysql:5.7 volumes: -...

Yes, it does not all have to be done in the backend. Typically the front end does some of the stuff in a OIDC flow. Also including refreshing authorization. I...

Implement assertDatastoreHasWorker. Test with `yarn enable-jobs` `yarn disable-jobs`

> could we have this maybe only if the PR is ready for review? Done now. As discussed after the presentation, it is not exactly clear how to proceed here....

> I like the idea of a `devdeploy` label. Draft state shouldn't matter. Can actions be triggered when a label has been added/removed? Yes, it is possible to run a...

You already implemented the necessary redirect. A redirect for the actual login only makes sense in the backend IMO since the front end is not involved. The application.conf problem should...

Making the first user of the orga admin could also be a separate issue, right? Or should this be adressed here?

> @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...

> 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)...

> 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...