Basic Authz Policy Seeding #2

New Issue

adam · 2023-07-04T12:36:41Z

adam commented

2023-07-04 12:36:41 +00:00

One of the main goals for this project is to be able to seed configuration for a downstream service. The Hub should be able to give a policy definition to the spoke-agent of a registered application.

The flow for this should look something like

Spoke-Agent reaaches out to /application/init
Hub responds with a JSON with hrefs to policy definition
Spoke-Agent hits policy definition endpoint
Spoke-Agent populates k8s config map in the namespace

From here we'll rely on client libraries to make use of the config maps, to actually put the policy into action.

One of the main goals for this project is to be able to seed configuration for a downstream service. The Hub should be able to give a policy definition to the spoke-agent of a registered application. The flow for this should look something like 1. Spoke-Agent reaaches out to /application/init 2. Hub responds with a JSON with hrefs to policy definition 3. Spoke-Agent hits policy definition endpoint 4. Spoke-Agent populates k8s config map in the namespace From here we'll rely on client libraries to make use of the config maps, to actually put the policy into action.

adam added this to the POC Finished milestone 2023-07-04 12:46:44 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/servicedemon#2