Alex Eftimie
Alex Eftimie
@freben > then on the server side have a small middleware at the very top that looks for the custom header and injects it again as an Authorization header so...
I can try an alternative implementation using microsoft/fetch-event-source. thanks for the pointer!
I can see that some of the plugins in [the list](https://github.com/backstage/backstage/issues/23015#issuecomment-1950966308) were moved unmodified to https://github.com/search?q=repo%3Abackstage%2Fcommunity-plugins%20Authorization&type=code will follow up with the remainder
https://github.com/backstage/backstage/pull/24861 and https://github.com/backstage/backstage/pull/24878 ready
Not fully completed (missing events and a finall checkup that no hardcoded indentityApi token remains)
@ggkoning first of all, in `packages/backend/src/index.ts`, you need: ``` ... const backend = createBackend(); backend.add(rootHttpRouterServiceFactory({ configure: ({ app, applyDefaults }) => { app.use((req, _, next) => { if (req.headers['backstage-authorization']) {...
@ggkoning thanks for offering. you can try to spot other frontend->backend clients that don't use the fetchApi or that hardcode the "Authorization" header. (backend->backend is fine) the events PR is...
I have the same question