Ben Lambert

@AnishAnil you're still going to keep the microsoft part, you're just going to implement your own resolver, although you still haven't answered if you have any users in the Backstage...

@zhammer I think that this makes sense, do you want to raise a PR for adding something to config?

@zhammer yep, I think something like that make sense! :pray:

@koalaty-code yes! Sorry, didn't see that this issue was still around. Thanks!

Hmm, what's going on in your custom version of the `TaskScheduler`? Wondering if there's some things which are not caught there which is causing the backend to crash. Upgrading the...

So one thing to note is that if you have tasks running in the scaffolder, and the backend crashes, which might not be the fault of the scaffolder, it might...

@laharshah I wanna come back to some of your `knex` config that I've been digging around with recently as we've seen some of these errors in tests in Github Actions...

It's also possible that this issue is actually pretty closely related to https://github.com/backstage/backstage/issues/19863 I wonder if this is something to do with the fact now that every backend plugin that...

The users in the catalog should come from the `GitLab` org provider, although if you want to allow signin without users already in the catalog you can follow [this documentation](https://backstage.io/docs/auth/identity-resolver#sign-in-without-users-in-the-catalog)

@yaziderman If you're running a more recent version of the catalog, it might also be worth installing the `catalog-logs` module to get more verbose logging. https://backstage.io/docs/features/software-catalog/configuration/#logging-errors