ECLK / ECLK/Results-Dist

Design user management process for results distribution

Open
#23 10 comments 0 reactions 0 assignees View on GitHub
Dominant language
Ballerina
Stars
13
Forks
7
PR merge metrics
No merged PRs in 30d

Description

Basic process:
- EC will register organizations who are able to subscribe
- The orgs need to be given access credentials
- Some orgs may not have proper SSL certificates - should we consider support HTTP and signing the payload? The data itself is not confidential but its important to have a tamper proof delivery model. Something like https://en.wikipedia.org/wiki/JSON_Web_Signature? An alternative is to allow orgs to upload a self-signed cert but unnecessary pain

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by turning the registration, credential, and delivery-integrity questions in this issue into agreed requirements; compare the HTTP/signing option with self-signed certificates and the linked JSON Web Signature reference. Done means the organization onboarding and tamper-proof delivery model are decided and documented.

Written by the indexing model from the issue text.

Assessment

Domain
authentication, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.