How to retrieve client_name when using DID identifier scheme?
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 112
- Forks
- 38
- Avg merge
- 12d 19h
- Merged PRs (30d)
- 4
Description
The requirements in Authorization Request
Other metadata parameters MUST be ignored unless a profile of this specification explicitly defines them as usable in the
client_metadataparameter.
In the case of using DIDs as client identifiers how should the wallet retrieve UX related information such as client_name, logo_uri and tos_uri?
Contributor guide
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.
Research direction
Start with the Authorization Request section linked in the issue, especially the rule about ignored metadata and the client_metadata parameter. Read the discussion thread to understand the unresolved alternatives for DID identifiers. Done means the specification or an explicitly identified profile clearly defines how wallets obtain client_name, logo_uri, and tos_uri.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, security
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100