This document explains how clients from the portal are handled.
The portal is a DBus service that exposes interfaces to request access to the PipeWire daemon to perform a certain set of functions. The PipeWire daemon runs outside the sandbox, the portal is a way for clients inside the sandbox to connect to and use PipeWire.
The PipeWire socket is not exposed in the sandbox. Instead, The portal connects to PipeWire on behalf of the client, informing PipeWire that this client is a portal-managed client. PipeWire can detect and enforce extra permission checks on the portal managed clients.
Once such portal is the camera portal that provides a PipeWire session to stream video from a camera.
Use Cases
New Portal Managed Clients Need Device Permissions Configured
When a new client is detected, the available objects need to be scanned and permissions configured for each of them.
Only the devices belonging to the media_roles given by the portal are considered.
New Devices Need To Be Made Visible To Portal Managed Clients
Newly created objects are made visible to a client when the client is allowed to interact with it.
Only the devices belonging to the media_roles given by the portal are considered.
Permissions For A Device Need To Be Revoked
The session manager listens to changes in the permissions of devices and will remove the client permissions accordingly.
Usually this is implemented by listening to the permission store DBus object. The desktop environment might provide a configuration panel where these permissions can be managed.
Design
The Portal
A sandboxed client cannot connect to PipeWire directly. Instead, it connects to the sandbox side of the portal which then connects the PipeWire daemon to configure the session. The portal then hands the file descriptor of the PipeWire connection to the client and the client can use this file descriptor to interface with the PipeWire session directly.
When the portal connects, it will set the following properties on the client object:
"pipewire.access.portal.is_portal" = truefor the connection of the portal itself (as opposed to a client managed by the portal)."pipewire.access.portal.app_id"the application ID of the client."pipewire.access.portal.media_roles"media roles of the client. Currently only"Camera"is defined.
Before returning the connection to a client, the portal configures minimal permissions on the client. No objects are initially visible. It is the task of the PipeWire Session Manager to make the objects in the graph visible, depending on the client's media_roles (see also PW_KEY_MEDIA_ROLE).
The PipeWire Portal Module
The PipeWire daemon uses the PipeWire Module: Portal to find the PID of the processes that owns the DBus name org.freedesktop.portal.Desktop (see the XDG Desktop Portal).
Client connections from this PID are tagged as PW_KEY_ACCESS "portal" (see PipeWire Module: Access). It will also set ALL permissions for this client so that it can resume.
The Client
A client can ask the portal for a connection to the PipeWire daemon.
The portal maintains an (unrestricted) connection to the PipeWire daemon with "pipewire.access.portal.is_portal" = true to identify the nodes the client needs access to. It then creates a new restricted connection for the client, tagged with additional information.
The file descriptor for this restricted connection is passed back to the client which can now make use of the resources it has been permitted to access.
The Session Manager
The session manager listens for new clients to appear. It will use the PW_KEY_ACCESS property to find portal connections. For client connections from the portal the session manager checks the requested media_roles and enables or disables access to the respective PipeWire objects. It might have to consult a database to decide what is allowed, for example the org.freedesktop.impl.portal.PermissionStore.
In the case of the XDG Desktop Portal, the portal itself queries the PermissionStore directly.
