radius-project / radius-project/radius

Secure communication between UCP and resource providers

Open
#8,083 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

maintenance triaged
Dominant language
Go
Stars
1.7k
Forks
137
Avg merge
1d 5h
Merged PRs (30d)
93

Description

Area for Improvement

We need to secure communication between UCP and the resource providers we have: Deployment Engine, Applications RP, and Dynamic RP.

As of now (24 Nov 2024), we do not have an authentication mechanism for communication between UCP and the resource providers.

Tasks of this issue:

  • Research authentication mechanisms and propose one for our case (e.g., mTLS).
  • Prepare a design document and present it in one of the design meetings.
  • Implement the changes.
  • Create/Update unit and functional tests.
Observed behavior

No authentication between UCP and resource providers.

Desired behavior

An authentication mechanism between UCP and resource providers.

Proposed Fix

This is an improvement that needs to be discussed in one of the design discussions.

rad Version

edge

Operating system

No response

Additional context

No response

Would you like to support us?
  • Yes, I would like to support you

AB#13746

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or implementation entry points are identified. Begin by researching authentication mechanisms for communication between UCP and the Deployment Engine, Applications RP, and Dynamic RP, then prepare a design document, present it in a design meeting, and define the unit and functional tests needed for the chosen approach.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
authentication, backend-api-design, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.