TransparentHealth/smh_app

Model Org-to-member relationships in the OIDC Provider (Not for MVP)

Open

#191 opened on Aug 30, 2019

View on GitHub
 (1 comment) (0 reactions) (2 assignees)CSS (3 forks)auto 404
enhancementhelp wantedquestion

Repository metrics

Stars
 (2 stars)
PR merge metrics
 (PR metrics pending)

Description

This means that Membership in an Organization will become part of the OIDC token and our profile.

The smh_app will receive this information as part of the id_tokenin a similary way this is done for OrgAgents.

smh_app and other applications may use a Membership API to add/remove people as members.

Contributor guide

Research direction
Investigate the existing OrgAgent implementation in the OIDC provider and replicate similar logic for Org to member relationships. Look at the Membership API endpoints to understand data flow.
Tech stack
None
Domain
backendauthentication
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
OIDCBackend development
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40