Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: add ResourceAccessScopeStrategy #806

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

zoop-btc
Copy link

Related to this hydra issue.

This scope strategy splits a scope into resources delimited with :.
Each resource can have dynamic values if it has the suffix -*.
The last resource can specify a verb delimited with ..

The hierarchy of the matcher and scope resources needs to be identical.

Examples:

  • users.* matches users.read
  • users.write does not match users.read
  • users:settings matches users:settings
  • users:settings does not match users:settings.read
  • users:client-*.read does match users:client-bar.read
  • users:client-* does not match users:client-bar.read
  • users:client-*.* does match users:client-foo.write

Open questions:
Should I make the resource/verb delimiter configurable? What about allowing dynamic resources?

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
@CLAassistant
Copy link

CLAassistant commented Mar 29, 2024

CLA assistant check
All committers have signed the CLA.

@medhost-chara
Copy link

medhost-chara commented May 15, 2024

Before I open a separate discussion, I wanted to check if there are plans for defining a scope matching strategy for use in ORY Hydra. As part of the Smart App Launch US HTI-1 Guidelines to support Smart App Launch 2.0.0 - the scope formats were updated to the following format: https://hl7.org/fhir/smart-app-launch/STU2/scopes-and-launch-context.html#scopes-for-requesting-clinical-data

patient.read > patient.r or patient.rs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants