Carry multiple Authentication Tokens

Open
#211 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by tracing the wen front end’s existing Google access-token flow for roster and document requests. Identify the rules and error paths needed for Canvas and Schoology tokens, with completion defined as per-request token selection and handling expired or unavailable tokens.

Written by the indexing model from the issue text.

Description

At present when users log into the wen front end they carry a single access token for Google which we use for doc and roster access. In order to incorporate Canvas and Schoology however we will need to carry around multiple tokens and control how those tokens are used on a per-request basis. This means augmenting the roster and document requests to select tokens based upon existing rules dynamically, and having a mechanism to trap errors when the tokens are expired or simply unavailable.

Dominant language
Python
Stars
12
Forks
11
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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.

More from ArgLab/writing_observer

All issues in ArgLab/writing_observer

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.