Patrik Oldsberg

@drodil yep thinking it's probably best to keep that behind more explicit config to exclude users tbh. Using rules you might want to trigger an alert if someone tries to...

Yep definitely something we want to add better support for in the catalog! 👍 No plans right now to work on this right now in the maintainer team though. There's...

Afaik this is tricky, see the original change here: https://github.com/backstage/backstage/pull/5769/files

Merged by mistake, reverted and replaced by #24777

Have you added the plugin to `packages/backend`? When you `yarn start` in the plugin folders you'll use a local setup for the plugin, but `yarn dev` in the repo root...

@eilonash92 yep it is right now, we'll likely adjust one of the two in the future so that they both match. Either not adding the frontend plugin to the app,...

@freben hmm, JWKS endpoints are used for more than just OIDC. I'm thinking that we consider that as an addition, but as a base feature set I think the existing...

Prolly need to be a bit more explicit though, JWKS endpoints don't always contain `.well-known`, e.g. https://login.microsoftonline.com/common/discovery/v2.0/keys

@freben not really tbh, we also link to it from `OWNERS.md`. It's a fairly common setup to only have a `GOVERNANCE.md` in a `*/community` repo.

Yep makes sense 👍 I'd argue that we might not need `require-user`? Or do you have a specific use-case in mind? And yep, `require` or w/e we call it would...