Error: Plugin doesn't work with the new backend architecture

[javier-fiore]

When we try to use this plugin whit the new backend architecture, we receive a 401 unauthorized when it try to access to circleCI api.

Maybe you must update this repo with the scaffolding created with create-app program to make it work with the new backstage.

[supersol]

@javier-fiore
Maybe this helps. Lots of googling brought me here. I think they just gave up supporting this plugin. I'm using the one from the older repo @backstage/plugin-circleci
And I also had this issue. So I solved it adding

    proxy:
      endpoints:
        /circleci/api:
          changeOrigin: true
          headers:
            Circle-Token: ${CIRCLECI_AUTH_TOKEN}
          target: https://circleci.com/api/v1.1
          credentials: dangerously-allow-unauthenticated

I have all the setup in local network so for me it's pretty safe. Backstage forced auth internally between plugins. I have no idea where do I need set those internal credentials, so I just allowed access without them.
https://backstage.io/docs/plugins/proxying/

[javier-fiore]

@javier-fiore Maybe this helps. Lots of googling brought me here. I think they just gave up supporting this plugin. I'm using the one from the older repo @backstage/plugin-circleci And I also had this issue. So I solved it adding

    proxy:
      endpoints:
        /circleci/api:
          changeOrigin: true
          headers:
            Circle-Token: ${CIRCLECI_AUTH_TOKEN}
          target: https://circleci.com/api/v1.1
          credentials: dangerously-allow-unauthenticated

I have all the setup in local network so for me it's pretty safe. Backstage forced auth internally between plugins. I have no idea where do I need set those internal credentials, so I just allowed access without them. https://backstage.io/docs/plugins/proxying/

It works, but I am afraid to use this kind of configuration. At this time, ti works as workaround, but i think that there is a bug here. Thanks a lot!

[phclark]

+1, requiring adopters to disable backend authentication shouldn't be an acceptable workaround for production systems. Looking through the code, it looks like this plugin uses the circleci-api package to make requests, overwriting the URL to use the backend proxy. I think it should be possible to use the Backstage IdentityApi to add the user's Backstage authentication information to the request so that the Backstage backend auth system doesn't return a 401, but would leave this up to the maintainers to decide the best path here.