Skip to content

Notification Sender - authentication may require both identities client & agent (user) #134

Open
@elf-pavlik

Description

@elf-pavlik

Previous drafts were using webid in Subscription Response (Webhook, LDN). Recently we changed it to sender.

Commonly solid authentication provides two identities:

  • client - the application (e.g. used by acp:client matcher)
  • agent - the end user (e.g. used by acp:agent matcher)

I think having just single WebID as sender doesn't support case where access policy on the target should be based on two identities client and agent. We should consider supporting providing both identities for the sender.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions