Skip to content

Add subject_uri_schemes_supported property to AS Metadata #227

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.

Sign up for GitHub

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

Open
acoburn wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Add subject_uri_schemes_supported property to AS Metadata #227

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
27 changes: 23 additions & 4 deletions lws10-core/Authorization.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -87,11 +87,26 @@ <h4>Authorization Server Metadata</h4>
</p>

<p>
An authorization server SHOULD advertise the subject tokens that it supports by including a <code>subject_token_types_supported</code>
entry in the server metadata document. This entry is a JSON array containing a list of valid <code>subject_token_type</code> values
that can be supplied at the authorization server's token endpoint.
In addition to the metadata defined in [[!RFC8414]], an LWS authorization server metadata document
defines the following parameters:
</p>

<ul>
<li>
<code>subject_token_types_supported</code>
OPTIONAL. JSON array containing a list of valid <code>subject_token_type</code> values
that can be supplied at the authorization server's token endpoint. An authorization server
SHOULD advertise the subject tokens that it supports by including this entry in the server metadata document.
</li>
<li>
<code>subject_uri_schemes_supported</code>
OPTIONAL. JSON array containing a list of URI scheme values for subject identifiers that the
authorization server supports. An authorization server SHOULD advertise the subject URI schemes
that it supports by including this entry in the server metadata document.
If omitted, the default value is <code>["https"]</code>.
</li>
</ul>

<p>
An example authorization server metadata resource is included below.
</p>
Expand All @@ -112,7 +127,11 @@ <h4>Authorization Server Metadata</h4>
"token"],
"subject_token_types_supported": [
"urn:ietf:params:oauth:token-type:jwt",
"urn:ietf:params:oauth:token-type:id-token"]
"urn:ietf:params:oauth:token-type:id-token"],
"subject_uri_schemes_supported": [
"did:web",
"did:key",
"https"]
}
</pre>

Expand Down
15 changes: 15 additions & 0 deletions lws10-core/IANA-Considerations.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -42,6 +42,21 @@ <h3>OAuth Authorization Server Metadata Registry</h3>
Specification Document(s): Section 5 of LWS-Auth
</li>
</ul>

<ul>
<li>
Metadata Name: subject_uri_schemes_supported
</li>
<li>
Metadata Description: JSON array containing a list of URI scheme values for subject identifiers that this authorization server supports
</li>
<li>
Change Controller: W3C
</li>
<li>
Specification Document(s): Section 5 of LWS-Auth
</li>
</ul>
</section>

<section id="iana-media-type-registry">
Expand Down
Loading