XML

Word

Printable

Epic Name:
Understand Requirements for Backstage/RHDH MCP server authentication and authorization
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Ready:
False
Epic Status:
To Do
Feature Link:
RHDHPLAN-390 - [MCP Server] Native Identity & Permission Enforcement for MCP Tools
Planning:

QE Needed, Docs Needed, TE Needed, Customer Facing, PX Needed
Hierarchy Progress Bar:

100% To Do, 0% In Progress, 0% Done
Intelligence Requested:
Market:

EPIC Goal

Understand Requirements for Backstage/RHDH MCP server authentication and authorization with RHDH frontend V2

Background/Feature Origin

Currently we have Static token authentication and no authorization for the RHDH MCP Server that is used as a dynamic plugin in RHDH

With RHDH Frontend V2, Dynamic Client Registration(DCR) will be available for authentication and we can explore this approach.