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

Add RS associated AS issuing Access Token #18

Merged
merged 15 commits into from
Jan 12, 2022

Conversation

elf-pavlik
Copy link
Member

@elf-pavlik elf-pavlik commented Aug 2, 2021

Once we merge #17 I'll rebase this one to only include relevant changes. This variant of sequence diagram introduces RS associated AS which issues an Access Token.

Screen Shot 2021-08-02 at 8 48 36

You can see alt block with two options

  1. directly exchange ID Token for Access Token - this would match basic approach of current Solid-OIDC
  2. exchange ID Token for chainable Ticket - this would allow pushing more claims before getting the Access Token
  3. one of the claims would be Data Grant from Solid Application Interoperability providing resource client authorization granted by the requesting party

@elf-pavlik
Copy link
Member Author

elf-pavlik commented Nov 15, 2021

preview of the diagram in the latest commit (click on the image to see higher res):

Screen Shot 2021-11-15 at 8 19 21

@elf-pavlik
Copy link
Member Author

The latest commits include updates to the text. It still misses describing the discovery of the Authorization Server and pushing OIDC ID Token as part of the Claim Token.

Latest diagram includes Client ID Document:

Screen Shot 2021-11-21 at 15 16 35

index.bs Outdated Show resolved Hide resolved
index.bs Outdated Show resolved Hide resolved
@elf-pavlik elf-pavlik marked this pull request as ready for review January 3, 2022 14:12
index.bs Outdated Show resolved Hide resolved
index.bs Outdated Show resolved Hide resolved
index.bs Outdated Show resolved Hide resolved
index.bs Outdated Show resolved Hide resolved
index.bs Outdated Show resolved Hide resolved
Copy link
Member

@acoburn acoburn left a comment

Choose a reason for hiding this comment

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

Generally, I am very supportive of this change. I'd like to see the UMA-specific sections to be changed a bit. That might mean something like: "if using UMA, an RS MUST do ...". We don't want a hard dependency on UMA, but describing it as a viable pattern would be very good.

index.bs Outdated Show resolved Hide resolved
index.bs Outdated Show resolved Hide resolved
index.bs Outdated Show resolved Hide resolved
elf-pavlik and others added 2 commits January 7, 2022 07:26
Co-authored-by: Zwifi <contact@zwifi.eu>
Co-authored-by: Aaron Coburn <acoburn@apache.org>
index.bs Show resolved Hide resolved
* Set UMA requirement as SHOULD
* Set OpenID profile as required for UMA servers
* Set WWW-Authenticate (as_uri) as MUST unless a
  different discovery mechanism is used
Copy link
Member Author

@elf-pavlik elf-pavlik left a comment

Choose a reason for hiding this comment

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

LGTM 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
next Next version introducing RS associated AS
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants