Additional metadata fields for Client Identifier Documents

未关闭
#204 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
领域
authentication

调研方向

首先审查 Client Identifier 文档元数据以及链接的 IANA OAuth client metadata registry 条目。然后将提议的 client_description 与 issue 中链接的 SAI application profile 讨论进行比较；完成这项工作需要达成一致的规范变更，并确认注册路径。

由索引模型根据 Issue 内容生成。

描述

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).

主要语言
Bikeshed
星标
26
派生
14
30 天内没有已合并 PR

贡献指南

这个仓库没有索引到贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

solid/solid-oidc 的其他 Issue

查看 solid/solid-oidc 的全部 Issue

相似的 Issue

更多 Security Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。