Additional metadata fields for Client Identifier Documents
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- authentication
Research direction
Start by reviewing the Client Identifier document metadata and the linked IANA OAuth client metadata registry entry. Then compare the proposed client_description with the SAI application profile discussion linked in the issue; done would require an agreed specification change and confirmation of the registration path.
Written by the indexing model from the issue text.
Description
I've been reading through some issues and other specifications, and I'm wondering if it would make sense or be possible for us to define some additional fields for the Client Identifier documents. In the SAI working group, they have the concept of an application description and application author. I think the latter is covered by the contacts field in the Client Identifier documents, but the former, a description of the client is currently only kind of covered by the client_uri value (the homepage).
I think it'd make sense to add a string value of client_description to the client identifier documents, I'm not sure if this is something this spec can do, as from what I understand it, the fields need to be registered in the IANA Registry, however, I think from a user perspective, being able to see a short textual description of the application may be helpful when displaying the consent screen.
This would, I think, reduce the gap between solid-oidc and SAI's need for an application profile document, as noted in https://github.com/solid/data-interoperability-panel/issues/210#issuecomment-953736998
(addendum: I did try to find an existing issue prior to opening this one, but didn't find anything that concretely was this specifically).
- Dominant language
- Bikeshed
- Stars
- 26
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from solid/solid-oidc
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
solid/solid-oidc#258 ·
-
doc: solid-oidc-primer editorial
Difficulty 1/5 Under an hour Newbie friendliness 75/100
solid/solid-oidc#144 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
solid/solid-oidc#238 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
solid/solid-oidc#237 · 1 comment · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
solid/solid-oidc#231 · 1 comment ·
All issues in solid/solid-oidc
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
docToolchain/docToolchain#1705 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
modelcontextprotocol/python-sdk#3566 ·
-
Mend: dependency security vulnerability status: needs triage 🕵️♀️
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
carbon-design-system/ibm-products#9907 ·
-
agent/security hive/hosted-available-lke648397-260827-5n31 security
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
canonical/paas-charm#368 · 1 comment ·