Story (Required)

As a consumer of road-core as upstream, we want to know how to configure road-core by-pass the authentication.

Background (Required)

In RHDH lightspeed, the plugin uses RHDH auth & RBAC: https://backstage.io/docs/auth/#identity-for-plugin-developers

we want to rely on RHDH Auth & RBAC, and by-pass the authentication in road-core

it does seem like road-core have a noop auth method created: https://github.com/road-core/service/blob/3ea924f4945c0677e3ba8576161b37fb14b15075/ols/src/auth/noop.py

setup the road-core env in both local & container

and try with the no-operation auth in road-core to verify it's able to by-pass the authentication with any API calls.

also record the configuration needs to be set in the rcsconfig.yaml:

https://github.com/road-core/service/blob/3ea924f4945c0677e3ba8576161b37fb14b15075/examples/rcsconfig.yaml#L88-L92

Out of scope

<Defines what is not included in this story>

Approach (Required)

<Description of the general technical path on how to achieve the goal of the story. Include details like json schema, class definitions>

Dependencies

<Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>

Acceptance Criteria (Required)

<Describe edge cases to consider when implementing the story and defining tests>

<Provides a required and minimum list of acceptance tests for this story. More is expected as the engineer implements this story>

documentation updates (design docs, release notes etc)
demo needed
SOP required
education module update (Filled by DEVAI team only)
R&D label required (Filled by DEVAI team only)

Done Checklist

Code is completed, reviewed, documented and checked in
Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
Continuous Delivery pipeline(s) is able to proceed with new code included
Customer facing documentation, API docs, design docs etc. are produced/updated, reviewed and published
Acceptance criteria are met
If the Grafana dashboard is updated, ensure the corresponding SOP is updated as well