Patrik Oldsberg

Yep, entity providers is the preferred pattern for ingesting additional entities. Definitely makes sense to migrate any such processors that don't currently have an equivalent provider. In many cases we...

@niallthomson Yep, right now you can register any type of location through a `Location` entity. That means that anyone with the ability to add a `Location` entity to the catalog...

Gonna close this since the issue seems to be resolved. @secustor for your particular case I'm not sure you need to use `createSpecializedBackend` btw, should be enough to `backend.add(customUrlReaderServiceFactory)` +...

What do you think about communicating the session details in-band within the WebSocket connection instead? That way we'd avoid the need to store this session state in the DB as...

@jamieklassen yep seems like a valid concern. I'm not entirely sure what the real differences are between a WebSocket connection flood vs e.g. a plain HTTP Slowloris DoS, but I...

@luchillo17 +1 to a cookie approach. My immediate thought is that we'd scope it to the plugin itself rather than a more deployment-wide approach. Something like this: 1. GET `/api/plugin-x/gimmie-cookie`...

With the new auth APIs in flight and another implementation in the signal backend, I'd suggest that we settle on using the `sec-websocket-protocol` header to carry a user token. It's...

@afscrome that one is actually just about to be closed by #14584, does that solution cover your use-case as well? If not I think it might be best to outline...

@Remyapraveen thank you for reporting! We'll need to add a redirect to `https://backstage.io/docs/features/software-catalog/` in the [microsite config](https://github.com/backstage/backstage/blob/e539649d803e590a639fd78e4be0ebe1eef02007/microsite-next/docusaurus.config.js#L100). Do you want to submit a PR?

Turned out to be a pretty widespread issue. I ended up shipping it in #16708 through https://github.com/backstage/backstage/issues/14574#issuecomment-1453263180