Look into authorization consistency

Open
#103 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
30/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Active
Tech stack
typescript

Research direction

Review the three authorization paths described in the issue and the overlapping access scenario in pull request #101. Compare PAT, client-claim, and OIDC-header authentication across the server interactions. Done means the overlap has a documented, agreed-upon authorization approach rather than an unresolved investigation.

Written by the indexing model from the issue text.

Description

There are multiple authorization paths in the server.

  1. RS <-> AS interactions where a PAT is required, following the UMA specification.
  2. Client claims during a token request.
  3. Other client interactions outside of the specifications, such as policy management and access requests. This uses standard OIDC headers.

The problem is if some of these overlap, which happened in https://github.com/SolidLabResearch/user-managed-access/pull/101, where the client wanted to access the list of registered resources. The current solution is to allow both the PAT flow, and standard client OIDC authentication, but it should be investigated if these can be more aligned since in the end both use OIDC tokens, but slightly differently.

Dominant language
TypeScript
Stars
9
Forks
4
Avg merge
4d 21h
Merged PRs (30d)
3

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 SolidLabResearch/user-managed-access

All issues in SolidLabResearch/user-managed-access

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.