You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 25, 2023. It is now read-only.
The first change moves us in the more direction of authorization to a generic resource, not just simply authenticating the user. The second change furthers this by distinguishing the resource owner from the subject of the resource.
We're missing a way to express who authorized this access. We should add an ownerDID claim.
ownerDID != subjectDID when the resource is NOT a set of claims about the party that authorized access. Eg. Acme Bank authorizes IRS access to credit card statements about Eve.
The text was updated successfully, but these errors were encountered:
resource owner
An OAuth resource owner that is the "user" in User-Managed Access. This is typically an end-user (a natural person) but it can also be a corporation or other legal person.
We could use "resourceOwner", but I'd be fine with "owner" as well.
We're recently dones some changes:
ConsentCredential
->AuthorizationCredential
(ref: Should use authorization terminology adapter#188).userDID
->subjectDID
(ref: PR feat: AuthorizationCredential Context #20 (comment)).The first change moves us in the more direction of authorization to a generic resource, not just simply authenticating the user. The second change furthers this by distinguishing the resource owner from the subject of the resource.
We're missing a way to express who authorized this access. We should add an
ownerDID
claim.ownerDID
!=subjectDID
when the resource is NOT a set of claims about the party that authorized access. Eg. Acme Bank authorizes IRS access to credit card statements about Eve.The text was updated successfully, but these errors were encountered: