Skip to content

document window-id and activation-token as well-known detail keys #619

@hsitter

Description

@hsitter

Is your feature request related to a problem? Please describe.
In KDE Plasma we have esoteric side channeling tech where applications can talk directly to the auth agent to inform it of the application's window-id (for window modality) and its activation-token (for wayland activation shenanigans). This is horribly hacky and brittle and I'd like to get rid of it.

Describe the solution you'd like
Seeing as we have a flexible details system it'd be cool if we could document some well known keys to fill in these two use cases. Specifically I'd like us to document something like this:

- polkit.window-id: An xdg-desktop-portal window identifier https://flatpak.github.io/xdg-desktop-portal/docs/window-identifiers.html identifying the window that issued the authentication request
- polkit.activation-token: A platform-specific activation token for wayland https://wayland.app/protocols/xdg-activation-v1

Describe alternatives you've considered
We could lift these arguments into the actual API, but I think that's a headache nobody wants to deal with :)

Additional context
https://invent.kde.org/plasma/polkit-kde-agent-1/-/blob/master/org.kde.Polkit1AuthAgent.xml?ref_type=heads

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