[2309519334] Upstream Reporter: BillKlineVT
Upstream issue status: Closed
Upstream description:

Describe the bug

Backstage 1.24.0 changed the backend auth which protects all routes by default by requiring authentication, as described in the docs here

When following the documentation for adding the orchestrator plugin, there is no mention of setting up tokens for this backend auth.

The error seen when attempting to access the Orchestrator page in Backstage is shown below:

It appears that the orchestrator plugin is not configured to work with the new Backstage backend auth system.

Expected Behavior

Starting Backstage with the orchestrator plugin enabled results in a functioning orchestrator page/service

What are the steps to reproduce this bug?

1. Install orchestrator plugin to Backstage 1.27.2 following the Readme section for the new backend
2. Start Backstage
3. Go to the Orchestrator page

Versions of software used and environment

Backstage 1.27.2 @janus-idp/backstage-plugin-orchestrator-backend 1.8.7 @janus-idp/backstage-plugin-orchestrator 1.12.6