consider support for OIDC self-issuer
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 26
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
as discussed on one of the calls and in https://github.com/solid/authentication-panel/issues/2#issuecomment-520950159, support for the OIDC magic issuer https://self-issued.me with a public key in the webid profile (same as WebID-TLS) would have several benefits:
- marginally easier to set up a bot identity on an ordinary static web server vs creating a
.well-known/openid-configurationand ajwksfile (plus saving two more serialized HTTP transactions to fetch them) - enables on-device authentication (for example, a native app on a mobile device) using the self-issuer workflow envisioned by OIDC
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.
Research direction
Start with the linked authentication-panel discussion and the OIDC Core Self-Issued section, then compare the proposed public-key-in-WebID-profile flow with the existing WebID-TLS approach. Define the required specification changes and interoperability or conformance criteria before implementation; completion should clearly describe the supported self-issuer workflow.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100