solid / solid/data-interoperability-panel
Use invitation to validate the source of an incoming request
Open
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 58
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
Handle reverse use case where invitation is used to validate the source of an incoming access request.
- Trevor sends an access request to Bob, masquerading with a webid and profile that makes him look like Alice.
- Bob sees the request, and uses the invitation flow to in reverse to confirm that the request is coming from alice.
cc: @elf-pavlik @angel-araya-jd @ericprud @jamiefiedler
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
No file, test, or entry point is identified. Start by tracing the invitation flow and the incoming access-request flow described in the issue, then determine how the reverse use case should validate the requester's identity. Done means the specification clearly defines this reverse invitation behavior and its validation outcome.
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