Skip to content

Auth scope changes#61

Open
RaggedStaff wants to merge 7 commits into
masterfrom
authScopeChanges
Open

Auth scope changes#61
RaggedStaff wants to merge 7 commits into
masterfrom
authScopeChanges

Conversation

@RaggedStaff

Copy link
Copy Markdown
Contributor

PR detailing changes to incorporate scope-based authorization within the DFC Standard

@RaggedStaff RaggedStaff self-assigned this Oct 2, 2025
@github-project-automation github-project-automation Bot moved this to Icebox ❄ in Tech meeting board Oct 2, 2025
@RaggedStaff RaggedStaff moved this from Icebox ❄ to To review ☕ in Tech meeting board Oct 2, 2025

@lecoqlibre lecoqlibre left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This work is not aligned with our efforts to move closer to the Solid international consensus especially our previous work on the WebID. For me the DFC should rather move to Solid-OIDC.

If this solution is a transition and a temporary-only solution it should be noticed.

Comment thread technical-specifications/authorization-strategy.md
| **Subject** | **Endpoints accessible with subject** |
| --- | --- |
| Enterprise | Enterprise, Address, SocialMedia, PhoneNumber, CustomerCategory, Coordination, Place |
| Product | TechnicalProduct, LocalizedProduct, SuppliedProduct, Catalog, CatalogItem, Offer, Price, Transformation, ConsumptionFlow, ProductionFlow |

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Split Price/Offer

@RaggedStaff

Copy link
Copy Markdown
Contributor Author

@simonLouvet requests:

  1. Further detail of why this is required (more detail of the Data Permissioning Module).
  2. Include details of dfc-t:assignedScope & dfc-t:requiredScope

@@ -0,0 +1,36 @@
# Authorization Strategy

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Recommendation


Furthermore it is recommended that RP's implment a data consent system, whereby data owners can grant (and revoke) access to these scopes for individual clients/users within the OIDC domain. For example a portal wishing to read data on a users Enterprise and Products, might request `ReadEnterprise` and `ReadProduct` access. The RP should record which Enterprises have authorized a specific client or user to which scopes.

The DFC community provides a web component that can support RP's with this workflow: the [Data Sharing Module](https://github.com/startin-blox/data-sharing-module/) has full instructions on how to implment & manage scope permissions for users on your platform.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Clarify SiB (not part of DFC Community) built DPMfor Coopcircuits (are part of DFC Community)

@RachL

RachL commented Nov 18, 2025

Copy link
Copy Markdown
Member

@lecoqlibre is there a documentation link/paragraph that we could add here to give info on how Solid-OIDC can answer permissions between users?

@lecoqlibre lecoqlibre left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK. There is still work to do but can start with this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: To review ☕

Development

Successfully merging this pull request may close these issues.

3 participants